Message

From simple-bounces@ietf.org Thu Dec 01 01:02:54 2005 Received: from localhost.cnri.reston.va.us ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1EhhWw-0005Cy-Ha; Thu, 01 Dec 2005 01:02:54 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1EhhWu-0005CV-6E for simple@megatron.ietf.org; Thu, 01 Dec 2005 01:02:52 -0500 Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id BAA23412 for ; Thu, 1 Dec 2005 01:02:05 -0500 (EST) Received: from szxga01-in.huawei.com ([61.144.161.53] helo=huawei.com) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1EhhrF-0008BY-De for simple@ietf.org; Thu, 01 Dec 2005 01:23:59 -0500 Received: from huawei.com (szxga01-in [172.24.2.3]) by szxga01-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 1.25 (built Mar 3 2004)) with ESMTP id <0IQT002EO20S8Z@szxga01-in.huawei.com> for simple@ietf.org; Thu, 01 Dec 2005 14:00:29 +0800 (CST) Received: from szxml02-in ([172.24.1.6]) by szxga01-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 1.25 (built Mar 3 2004)) with ESMTP id <0IQT005OD20S9R@szxga01-in.huawei.com> for simple@ietf.org; Thu, 01 Dec 2005 14:00:28 +0800 (CST) Received: from m24697A ([10.164.10.31]) by szxml02-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 1.25 (built Mar 3 2004)) with ESMTPA id <0IQT00BUR23SJY@szxml02-in.huawei.com> for simple@ietf.org; Thu, 01 Dec 2005 14:02:16 +0800 (CST) Date: Thu, 01 Dec 2005 13:52:13 +0800 From: Lunjian Mu To: simple@ietf.org Message-id: <015501c5f63b$610f8e80$1f0aa40a@china.huawei.com> MIME-version: 1.0 X-MIMEOLE: Produced By Microsoft MimeOLE V6.00.2900.2180 X-Mailer: Microsoft Outlook Express 6.00.2900.2180 X-Priority: 3 X-MSMail-priority: Normal X-Spam-Score: 0.2 (/) X-Scan-Signature: b19722fc8d3865b147c75ae2495625f2 Subject: [Simple] the status of chat document X-BeenThere: simple@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: SIP for Instant Messaging and Presence Leveraging Extensions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============1623126495==" Sender: simple-bounces@ietf.org Errors-To: simple-bounces@ietf.org This is a multi-part message in MIME format. --===============1623126495== Content-type: multipart/alternative; boundary="Boundary_(ID_K8jqKnDzmY2i3CioYGhHUw)" This is a multi-part message in MIME format. --Boundary_(ID_K8jqKnDzmY2i3CioYGhHUw) Content-type: text/plain; charset=gb2312 Content-Transfer-Encoding: 7BIT Hi All, Who can tell me the status of documents:draft-niemi-simple-chat-03.txt. A new version will be published or not ? Thanks and Best regards, Lunjian Mu --Boundary_(ID_K8jqKnDzmY2i3CioYGhHUw) Content-type: text/html; charset=gb2312 Content-Transfer-Encoding: 7BIT

Hi All,

Who can tell me the status of documents:draft-niemi-simple-chat-03.txt. A new version will be published or not ?

Thanks and Best regards,

Lunjian Mu

--Boundary_(ID_K8jqKnDzmY2i3CioYGhHUw)-- --===============1623126495== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ Simple mailing list Simple@ietf.org https://www1.ietf.org/mailman/listinfo/simple --===============1623126495==-- From simple-bounces@ietf.org Thu Dec 01 03:09:13 2005 Received: from localhost.cnri.reston.va.us ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1EhjVB-0008QT-Ry; Thu, 01 Dec 2005 03:09:13 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1EhjV9-0008QN-Dl for simple@megatron.ietf.org; Thu, 01 Dec 2005 03:09:11 -0500 Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id DAA04585 for ; Thu, 1 Dec 2005 03:08:24 -0500 (EST) Received: from mgw-ext04.nokia.com ([131.228.20.96]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1EhjpZ-0003eZ-Uf for simple@ietf.org; Thu, 01 Dec 2005 03:30:19 -0500 Received: from esebh108.NOE.Nokia.com (esebh108.ntc.nokia.com [172.21.143.145]) by mgw-ext04.nokia.com (Switch-3.1.7/Switch-3.1.7) with ESMTP id jB18402t009571 for ; Thu, 1 Dec 2005 10:09:04 +0200 Received: from esebh001.NOE.Nokia.com ([172.21.138.28]) by esebh108.NOE.Nokia.com with Microsoft SMTPSVC(6.0.3790.1830); Thu, 1 Dec 2005 09:56:11 +0200 Received: from mgw-int2.ntc.nokia.com ([172.21.143.97]) by esebh001.NOE.Nokia.com with Microsoft SMTPSVC(5.0.2195.6881); Thu, 1 Dec 2005 09:56:10 +0200 Received: from kusti.research.nokia.com (mgw.research.nokia.com [172.21.56.13]) by mgw-int2.ntc.nokia.com (Switch-2.2.8/Switch-2.2.8) with ESMTP id jB17uAP26999 for ; Thu, 1 Dec 2005 09:56:10 +0200 (EET) Received: from [172.21.34.145] (hed034-145.research.nokia.com [172.21.34.145]) by kusti.research.nokia.com (Postfix) with ESMTP id EF9A193B85 for ; Thu, 1 Dec 2005 09:56:09 +0200 (EET) Message-ID: <438EAC99.5090605@nokia.com> Date: Thu, 01 Dec 2005 09:56:09 +0200 From: Jari Urpalainen User-Agent: Mozilla Thunderbird 1.0.7-1.1.fc4 (X11/20050929) X-Accept-Language: en-us, en MIME-Version: 1.0 To: simple@ietf.org Subject: Re: [Simple] I-D ACTION:draft-ietf-simple-xml-patch-ops-00.txt Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-OriginalArrivalTime: 01 Dec 2005 07:56:10.0772 (UTC) FILETIME=[B19CD540:01C5F64C] X-Spam-Score: 0.0 (/) X-Scan-Signature: b19722fc8d3865b147c75ae2495625f2 Content-Transfer-Encoding: 7bit X-BeenThere: simple@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: SIP for Instant Messaging and Presence Leveraging Extensions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: simple-bounces@ietf.org Errors-To: simple-bounces@ietf.org Hi all! Changes since the individual version: -fixed a bug when replacing a comment or a PI node; a "< " character can be present within them, within text nodes it must be escaped -clarified attribute value and text node replace behavior when the replacement text is empty -added some conventions used in this memo which don't exist e.g. in the XPath 1.0 spec -clarified that the root node of a document as well as the full XML prolog cannot be patched with XPath semantics -absolute location paths in XPath selector values are allowed but not encouraged -added a patch element type for text content patching. This is still somewhat controversial mostly because of ipr issues. However, it was just added in order to show how to use it if some application really wants/needs it. AFAIK vcdiff seems to be the most sane way to handle these, but does anybody know whether the ipr limits its usage only to e.g. rfc3229 ? -did not include multi-select "msel" selector which could be used e.g. to remove multiple attributes or elements with one patch operation request. The reference implementation at includes it, however. The possible nested element case has to be handled then, but it is mostly not included in the spec because I can't see enough motivation for it. If there's really need for it it can be done in an extension later. The same can be said e.g. about a move operation. A couple of other nits here and there but I'd really appreciate some feedback/comments. br, Jari _______________________________________________ Simple mailing list Simple@ietf.org https://www1.ietf.org/mailman/listinfo/simple From simple-bounces@ietf.org Thu Dec 01 09:13:25 2005 Received: from localhost.cnri.reston.va.us ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1EhpBd-0006v1-Ej; Thu, 01 Dec 2005 09:13:25 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1EhpBc-0006ug-M1 for simple@megatron.ietf.org; Thu, 01 Dec 2005 09:13:24 -0500 Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA24933 for ; Thu, 1 Dec 2005 09:12:37 -0500 (EST) Received: from smtp4.clb.oleane.net ([213.56.31.20]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1EhpW6-0006y7-Iv for simple@ietf.org; Thu, 01 Dec 2005 09:34:35 -0500 Received: from Pavillonquatre ([194.3.133.88]) (authenticated) by smtp4.clb.oleane.net with ESMTP id jB1ECxKQ026424 for ; Thu, 1 Dec 2005 15:12:59 +0100 Message-Id: <200512011412.jB1ECxKQ026424@smtp4.clb.oleane.net> From: "Chantal Ladouce" To: Date: Thu, 1 Dec 2005 15:12:25 +0100 MIME-Version: 1.0 X-Mailer: Microsoft Office Outlook, Build 11.0.5510 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.2180 Thread-Index: AcX2gUEkChhPKa49RHeKanl9/ZWT/g== X-Spam-Score: 0.0 (/) X-Scan-Signature: 093efd19b5f651b2707595638f6c4003 Subject: [Simple] Wireless/WiFi Convergence Conference - Call for Papers X-BeenThere: simple@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: SIP for Instant Messaging and Presence Leveraging Extensions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============1597133602==" Sender: simple-bounces@ietf.org Errors-To: simple-bounces@ietf.org This is a multi-part message in MIME format. --===============1597133602== Content-Type: multipart/alternative; boundary="----=_NextPart_000_011D_01C5F689.A3865750" This is a multi-part message in MIME format. ------=_NextPart_000_011D_01C5F689.A3865750 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit The Wireless/WiFi Convergence Conference will be held in Paris on May 16 to May 19, 2006 http://www.upperside.fr/wirelessconvergence2006/wwconvergence2006cfp.htm It is still time to submit proposals. Organizers are looking for UMA papers. ------=_NextPart_000_011D_01C5F689.A3865750 Content-Type: text/html; charset="us-ascii" Content-Transfer-Encoding: quoted-printable

The Wireless/WiFi Convergence = Conference will be held in Paris on May 16 to May 19, 2006

http://www.upperside.fr/wirelessconvergence2006/wwconvergence200= 6cfp.htm

It is still time to submit proposals. = Organizers are looking for UMA papers.

------=_NextPart_000_011D_01C5F689.A3865750-- --===============1597133602== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ Simple mailing list Simple@ietf.org https://www1.ietf.org/mailman/listinfo/simple --===============1597133602==-- From simple-bounces@ietf.org Fri Dec 02 06:28:42 2005 Received: from localhost.cnri.reston.va.us ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1Ei95m-0006pb-Dv; Fri, 02 Dec 2005 06:28:42 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1Ei95k-0006kD-Bj for simple@megatron.ietf.org; Fri, 02 Dec 2005 06:28:40 -0500 Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id GAA09967 for ; Fri, 2 Dec 2005 06:27:52 -0500 (EST) Received: from hq-smtp-01.telio.no ([82.196.203.118]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1Ei9QO-00034T-Jd for simple@ietf.org; Fri, 02 Dec 2005 06:50:01 -0500 Received: from office-srv-04.HQ.TELIO.NO (unknown [192.168.1.221]) by hq-smtp-01.telio.no (Postfix) with ESMTP id AAEB4194476 for ; Fri, 2 Dec 2005 12:28:20 +0100 (CET) Received: from [192.168.1.67] ([192.168.1.67]) by office-srv-04.HQ.TELIO.NO with Microsoft SMTPSVC(6.0.3790.1830); Fri, 2 Dec 2005 12:27:49 +0100 Mime-Version: 1.0 (Apple Message framework v623) Content-Transfer-Encoding: 7bit Message-Id: <5c8b9b01e3f39cd47e410403752cc8fd@telio.no> Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed To: Simple WG From: Hisham Khartabil Date: Fri, 2 Dec 2005 12:27:56 +0100 X-Mailer: Apple Mail (2.623) X-OriginalArrivalTime: 02 Dec 2005 11:27:49.0062 (UTC) FILETIME=[6CCBDE60:01C5F733] X-Spam-Score: 0.0 (/) X-Scan-Signature: 7a6398bf8aaeabc7a7bb696b6b0a2aad Content-Transfer-Encoding: 7bit Subject: [Simple] WGLC: User Agent Capability Extension to PIDF (prescaps) X-BeenThere: simple@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: SIP for Instant Messaging and Presence Leveraging Extensions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: simple-bounces@ietf.org Errors-To: simple-bounces@ietf.org The WG chairs would like to start a Working Group Last Call on the following drafts: http://www.ietf.org/internet-drafts/draft-ietf-simple-prescaps-ext -05.txt This WGLC will end on December 16th, 2005. Please send your comments to this mailing list and to the authors. Thanks, Hisham _______________________________________________ Simple mailing list Simple@ietf.org https://www1.ietf.org/mailman/listinfo/simple From simple-bounces@ietf.org Mon Dec 05 13:31:14 2005 Received: from localhost.cnri.reston.va.us ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1EjL7K-00021K-Ry; Mon, 05 Dec 2005 13:31:14 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1EjL7J-000214-5P for simple@megatron.ietf.org; Mon, 05 Dec 2005 13:31:13 -0500 Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA24213 for ; Mon, 5 Dec 2005 13:30:21 -0500 (EST) Received: from mxgate1.brooktrout.com ([204.176.74.10]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1EjLSb-0003yL-3D for simple@ietf.org; Mon, 05 Dec 2005 13:53:16 -0500 X-IronPort-AV: i="3.99,217,1131339600"; d="scan'208"; a="23679241:sNHT27708192" X-MimeOLE: Produced By Microsoft Exchange V6.5 Content-class: urn:content-classes:message MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable Date: Mon, 5 Dec 2005 13:31:00 -0500 Message-ID: <330A23D8336C0346B5C1A5BB1966664701B8D4E8@ATLANTIS.Brooktrout.com> Thread-Topic: IMDN Issue #1: Security of IMDN Thread-Index: AcX5ygqNRz99IFFbS4ezLwACE5TCZg== From: "Burger, Eric" To: X-Spam-Score: 0.0 (/) X-Scan-Signature: 2870a44b67ee17965ce5ad0177e150f4 Content-Transfer-Encoding: quoted-printable Subject: [Simple] IMDN Issue #1: Security of IMDN X-BeenThere: simple@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: SIP for Instant Messaging and Presence Leveraging Extensions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: simple-bounces@ietf.org Errors-To: simple-bounces@ietf.org Proposal is that if the body of the message was encrypted or signed, the IMDN MUST be encrypted or signed, otherwise it MAY be plain text. Any dissent? _______________________________________________ Simple mailing list Simple@ietf.org https://www1.ietf.org/mailman/listinfo/simple From simple-bounces@ietf.org Mon Dec 05 13:32:07 2005 Received: from localhost.cnri.reston.va.us ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1EjL8B-00023C-O2; Mon, 05 Dec 2005 13:32:07 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1EjL8A-000236-5w for simple@megatron.ietf.org; Mon, 05 Dec 2005 13:32:06 -0500 Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA24258 for ; Mon, 5 Dec 2005 13:31:15 -0500 (EST) Received: from mxgate1.brooktrout.com ([204.176.74.10]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1EjLTV-0003zs-R1 for simple@ietf.org; Mon, 05 Dec 2005 13:54:10 -0500 X-IronPort-AV: i="3.99,217,1131339600"; d="scan'208"; a="23679274:sNHT39027960" X-MimeOLE: Produced By Microsoft Exchange V6.5 Content-class: urn:content-classes:message MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable Date: Mon, 5 Dec 2005 13:32:06 -0500 Message-ID: <330A23D8336C0346B5C1A5BB1966664701B8D4EC@ATLANTIS.Brooktrout.com> Thread-Topic: IMDN Issue #2: Date Stamp in IMDN Thread-Index: AcX5yjGbTvHpTktkRoSUg2udUTZnug== From: "Burger, Eric" To: X-Spam-Score: 0.0 (/) X-Scan-Signature: 0f1ff0b0158b41ac6b9548d0972cdd31 Content-Transfer-Encoding: quoted-printable Subject: [Simple] IMDN Issue #2: Date Stamp in IMDN X-BeenThere: simple@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: SIP for Instant Messaging and Presence Leveraging Extensions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: simple-bounces@ietf.org Errors-To: simple-bounces@ietf.org Add a date element to the IMDN. Does anyone care? I don't, so it goes in unless someone besides me squeaks. _______________________________________________ Simple mailing list Simple@ietf.org https://www1.ietf.org/mailman/listinfo/simple From simple-bounces@ietf.org Mon Dec 05 13:34:01 2005 Received: from localhost.cnri.reston.va.us ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1EjLA1-0002BY-RQ; Mon, 05 Dec 2005 13:34:01 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1EjLA0-0002BQ-S1 for simple@megatron.ietf.org; Mon, 05 Dec 2005 13:34:00 -0500 Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA24477 for ; Mon, 5 Dec 2005 13:33:10 -0500 (EST) Received: from mxgate1.brooktrout.com ([204.176.74.10]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1EjLVL-00043x-AC for simple@ietf.org; Mon, 05 Dec 2005 13:56:04 -0500 X-IronPort-AV: i="3.99,217,1131339600"; d="scan'208"; a="23679348:sNHT34702308" X-MimeOLE: Produced By Microsoft Exchange V6.5 Content-class: urn:content-classes:message MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable Date: Mon, 5 Dec 2005 13:33:59 -0500 Message-ID: <330A23D8336C0346B5C1A5BB1966664701B8D4F5@ATLANTIS.Brooktrout.com> Thread-Topic: IMDN Issue #4: Disposition-Notification-To Thread-Index: AcX5ynUV4F4y0FV2TOOptgnvfffYhg== From: "Burger, Eric" To: X-Spam-Score: 0.2 (/) X-Scan-Signature: 08e48e05374109708c00c6208b534009 Content-Transfer-Encoding: quoted-printable Subject: [Simple] IMDN Issue #4: Disposition-Notification-To X-BeenThere: simple@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: SIP for Instant Messaging and Presence Leveraging Extensions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: simple-bounces@ietf.org Errors-To: simple-bounces@ietf.org IETF 64 SIMPLE meeting consensus in room was to take out 3rd-party or 3rd-party transport notifications *for now*. Proposal is to simply have the presence of a Disposition-Notification header, leaving the possibility for adding a URI in the future (and restoring the mechanism from the current draft). Anyone need this functionality today? _______________________________________________ Simple mailing list Simple@ietf.org https://www1.ietf.org/mailman/listinfo/simple From simple-bounces@ietf.org Mon Dec 05 14:05:18 2005 Received: from localhost.cnri.reston.va.us ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1EjLeI-0002dn-Un; Mon, 05 Dec 2005 14:05:18 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1EjLeG-0002cl-UL for simple@megatron.ietf.org; Mon, 05 Dec 2005 14:05:16 -0500 Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA27864 for ; Mon, 5 Dec 2005 14:04:26 -0500 (EST) Received: from mxgate1.brooktrout.com ([204.176.74.10]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1EjLzb-0005A5-Mv for simple@ietf.org; Mon, 05 Dec 2005 14:27:20 -0500 X-IronPort-AV: i="3.99,217,1131339600"; d="scan'208"; a="23680761:sNHT28287576" X-MimeOLE: Produced By Microsoft Exchange V6.5 Content-class: urn:content-classes:message MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable Date: Mon, 5 Dec 2005 14:05:11 -0500 Message-ID: <330A23D8336C0346B5C1A5BB1966664701B8D58E@ATLANTIS.Brooktrout.com> Thread-Topic: IMDN Issue #5: "deleted" state Thread-Index: AcX5ztDsaZxE20unQbm1+hx67CEAPQ== From: "Burger, Eric" To: X-Spam-Score: 0.0 (/) X-Scan-Signature: 08e48e05374109708c00c6208b534009 Content-Transfer-Encoding: quoted-printable Subject: [Simple] IMDN Issue #5: "deleted" state X-BeenThere: simple@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: SIP for Instant Messaging and Presence Leveraging Extensions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: simple-bounces@ietf.org Errors-To: simple-bounces@ietf.org I had proposed dropping the deleted state, as it (1) did not make sense to me in an IM context and (2) has a ton of privacy implications. HOWEVER, it was mentioned that someone thought someone needed the "deleted" disposition. They thought they heard that someone in Paris (IETF 63) said they needed it. Speak now, or "deleted" will be deleted from the next draft. _______________________________________________ Simple mailing list Simple@ietf.org https://www1.ietf.org/mailman/listinfo/simple From simple-bounces@ietf.org Tue Dec 06 00:17:10 2005 Received: from localhost.cnri.reston.va.us ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1EjVCQ-0007Tv-52; Tue, 06 Dec 2005 00:17:10 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1EjVCP-0007TR-FK for simple@megatron.ietf.org; Tue, 06 Dec 2005 00:17:09 -0500 Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id AAA05495 for ; Tue, 6 Dec 2005 00:16:19 -0500 (EST) Received: from sj-iport-4.cisco.com ([171.68.10.86]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1EjVXq-00020V-Ia for simple@ietf.org; Tue, 06 Dec 2005 00:39:18 -0500 Received: from sj-core-4.cisco.com ([171.68.223.138]) by sj-iport-4.cisco.com with ESMTP; 05 Dec 2005 21:17:01 -0800 Received: from vtg-um-e2k4.sj21ad.cisco.com (vtg-um-e2k4.cisco.com [171.70.93.57]) by sj-core-4.cisco.com (8.12.10/8.12.6) with ESMTP id jB65Gwpf023869 for ; Mon, 5 Dec 2005 21:16:58 -0800 (PST) Received: from 10.21.83.244 ([10.21.83.244]) by vtg-um-e2k4.sj21ad.cisco.com ([171.70.93.57]) with Microsoft Exchange Server HTTP-DAV ; Tue, 6 Dec 2005 05:16:58 +0000 User-Agent: Microsoft-Entourage/11.2.1.051004 Date: Mon, 05 Dec 2005 21:17:04 -0800 From: Cullen Jennings To: "simple@ietf.org" Message-ID: Thread-Topic: draft-ietf-simple-xml-patch-ops-00 Thread-Index: AcX6JEtbiip/kWYXEdqgngARJEEJ/A== In-Reply-To: Mime-version: 1.0 Content-type: text/plain; charset="US-ASCII" Content-transfer-encoding: 7bit X-Spam-Score: 0.0 (/) X-Scan-Signature: a2c12dacc0736f14d6b540e805505a86 Content-Transfer-Encoding: 7bit Subject: [Simple] draft-ietf-simple-xml-patch-ops-00 X-BeenThere: simple@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: SIP for Instant Messaging and Presence Leveraging Extensions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: simple-bounces@ietf.org Errors-To: simple-bounces@ietf.org I was somewhat surprised to see this as a WG item. When do we use this and when do we use xcap? I was also sort of wondering about how to deal with the issues of elements that used name spaces inside of the data portion of attributes. For example... if I have namesace xmlns:z="urn:foo" then I have sel="z:doc" Would I ever have the case where the some xml parser library changed my namespace to xmlns:z="urn:foo" (it would do this perhaps because x was already in use)? If this happened, it seems like the "z:doc" would not get changed to "x:doc" and things would break badly. Thoughts? Is this a problem or is it all avoided some how? On 11/30/05 12:50 PM, "Internet-Drafts@ietf.org" wrote: > 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. > > Title : An Extensible Markup Language (XML) Patch > Operations Framework Utilizing XML Path > Language (XPath) Selectors > Author(s) : J. Urpalainen > Filename : draft-ietf-simple-xml-patch-ops-00.txt > Pages : 21 > Date : 2005-11-30 > > Extensible Markup Language (XML) documents are widely used as > containers for the exchange and storage of arbitrary data in today's > systems. Updates to this data require transporting of the entire XML > document between hosts, unless there's a mechanism that allows > exchanging only the updates of XML documents. This document > describes an XML patch framework utilizing XML Path language (XPath) > selectors. With the aid of these selector values and updated data > content a set of patches can then be applied to an existing initial > XML document. > > A URL for this Internet-Draft is: > http://www.ietf.org/internet-drafts/draft-ietf-simple-xml-patch-ops-00.txt > > To remove yourself from the I-D Announcement list, send a message to > i-d-announce-request@ietf.org with the word unsubscribe in the body of the > message. > You can also visit https://www1.ietf.org/mailman/listinfo/I-D-announce > to change your subscription settings. > > > Internet-Drafts are also available by anonymous FTP. Login with the username > "anonymous" and a password of your e-mail address. After logging in, > type "cd internet-drafts" and then > "get draft-ietf-simple-xml-patch-ops-00.txt". > > A list of Internet-Drafts directories can be found in > http://www.ietf.org/shadow.html > or ftp://ftp.ietf.org/ietf/1shadow-sites.txt > > > Internet-Drafts can also be obtained by e-mail. > > Send a message to: > mailserv@ietf.org. > In the body type: > "FILE /internet-drafts/draft-ietf-simple-xml-patch-ops-00.txt". > > NOTE: The mail server at ietf.org can return the document in > MIME-encoded form by using the "mpack" utility. To use this > feature, insert the command "ENCODING mime" before the "FILE" > command. To decode the response(s), you will need "munpack" or > a MIME-compliant mail reader. Different MIME-compliant mail readers > exhibit different behavior, especially when dealing with > "multipart" MIME messages (i.e. documents which have been split > up into multiple messages), so check your local documentation on > how to manipulate these messages. > > > Below is the data which will enable a MIME compliant mail reader > implementation to automatically retrieve the ASCII version of the > Internet-Draft. > Content-Type: text/plain > Content-ID: <2005-11-30114220.I-D@ietf.org> > > _______________________________________________ > I-D-Announce mailing list > I-D-Announce@ietf.org > https://www1.ietf.org/mailman/listinfo/i-d-announce _______________________________________________ Simple mailing list Simple@ietf.org https://www1.ietf.org/mailman/listinfo/simple From simple-bounces@ietf.org Tue Dec 06 16:30:24 2005 Received: from localhost.cnri.reston.va.us ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1EjkOG-0007W3-J0; Tue, 06 Dec 2005 16:30:24 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1EjkOE-0007VE-Pl for simple@megatron.ietf.org; Tue, 06 Dec 2005 16:30:22 -0500 Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA24683 for ; Tue, 6 Dec 2005 16:29:30 -0500 (EST) Received: from magus.nostrum.com ([69.5.195.2] helo=nostrum.com ident=root) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1Ejkjn-0002FX-LK for simple@ietf.org; Tue, 06 Dec 2005 16:52:40 -0500 Received: from [10.240.21.119] (m815f36d0.tmodns.net [208.54.95.129]) (authenticated bits=0) by nostrum.com (8.12.11/8.12.11) with ESMTP id jB6LTtSs060829 (version=TLSv1/SSLv3 cipher=RC4-SHA bits=128 verify=NO); Tue, 6 Dec 2005 15:29:57 -0600 (CST) (envelope-from rjsparks@nostrum.com) In-Reply-To: References: Mime-Version: 1.0 (Apple Message framework v746.2) Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed Message-Id: Content-Transfer-Encoding: 7bit From: Robert Sparks Subject: Re: [Simple] draft-ietf-simple-xml-patch-ops-00 Date: Tue, 6 Dec 2005 15:27:44 -0600 To: Cullen Jennings X-Mailer: Apple Mail (2.746.2) Received-SPF: pass (nostrum.com: 208.54.95.129 is authenticated by a trusted mechanism) X-Spam-Score: 2.9 (++) X-Scan-Signature: 42e3ed3f10a1d8bef690f09da16f507a Content-Transfer-Encoding: 7bit Cc: "simple@ietf.org" X-BeenThere: simple@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: SIP for Instant Messaging and Presence Leveraging Extensions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: simple-bounces@ietf.org Errors-To: simple-bounces@ietf.org On Dec 5, 2005, at 11:17 PM, Cullen Jennings wrote: > > I was somewhat surprised to see this as a WG item. When do we use > this and > when do we use xcap? This draft is intended to be what the group agreed to adopt as the solution for xcap-diff and the partial-* work based on the output of the patch bof and the SIMPLE WG discussion in Vancouver. It went beyond its mandate including patch operations for general text elements - this is something the group explicitly decided to not try to tackle by my memory. I can see your confusion given that the draft doesn't reference partial at all. Jari - could you provide a revision quicky that includes a section pointing to how this would be used with xcap and with partial? All - comment on the text modifying proposal quickly. Unless there is a very strong "Oh yeah - we all want to do this this way", and soon, I will ask Jari to remove this mechanism from this draft and return to exactly the scope we agreed to in Vancouver. RjS > > I was also sort of wondering about how to deal with the issues of > elements > that used name spaces inside of the data portion of attributes. For > example... > > if I have namesace xmlns:z="urn:foo" > > then I have sel="z:doc" > > Would I ever have the case where the some xml parser library > changed my > namespace to xmlns:z="urn:foo" (it would do this perhaps because x was > already in use)? If this happened, it seems like the "z:doc" would > not get > changed to "x:doc" and things would break badly. > > Thoughts? Is this a problem or is it all avoided some how? > > > On 11/30/05 12:50 PM, "Internet-Drafts@ietf.org" Drafts@ietf.org> > wrote: > >> 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. >> >> Title : An Extensible Markup Language (XML) Patch >> Operations Framework Utilizing XML Path >> Language (XPath) Selectors >> Author(s) : J. Urpalainen >> Filename : draft-ietf-simple-xml-patch-ops-00.txt >> Pages : 21 >> Date : 2005-11-30 >> >> Extensible Markup Language (XML) documents are widely used as >> containers for the exchange and storage of arbitrary data in >> today's >> systems. Updates to this data require transporting of the >> entire XML >> document between hosts, unless there's a mechanism that allows >> exchanging only the updates of XML documents. This document >> describes an XML patch framework utilizing XML Path language >> (XPath) >> selectors. With the aid of these selector values and updated data >> content a set of patches can then be applied to an existing >> initial >> XML document. >> >> A URL for this Internet-Draft is: >> http://www.ietf.org/internet-drafts/draft-ietf-simple-xml-patch- >> ops-00.txt >> >> To remove yourself from the I-D Announcement list, send a message to >> i-d-announce-request@ietf.org with the word unsubscribe in the >> body of the >> message. >> You can also visit https://www1.ietf.org/mailman/listinfo/I-D- >> announce >> to change your subscription settings. >> >> >> Internet-Drafts are also available by anonymous FTP. Login with >> the username >> "anonymous" and a password of your e-mail address. After logging in, >> type "cd internet-drafts" and then >> "get draft-ietf-simple-xml-patch-ops-00.txt". >> >> A list of Internet-Drafts directories can be found in >> http://www.ietf.org/shadow.html >> or ftp://ftp.ietf.org/ietf/1shadow-sites.txt >> >> >> Internet-Drafts can also be obtained by e-mail. >> >> Send a message to: >> mailserv@ietf.org. >> In the body type: >> "FILE /internet-drafts/draft-ietf-simple-xml-patch-ops-00.txt". >> >> NOTE: The mail server at ietf.org can return the document in >> MIME-encoded form by using the "mpack" utility. To use this >> feature, insert the command "ENCODING mime" before the "FILE" >> command. To decode the response(s), you will need "munpack" or >> a MIME-compliant mail reader. Different MIME-compliant mail readers >> exhibit different behavior, especially when dealing with >> "multipart" MIME messages (i.e. documents which have been split >> up into multiple messages), so check your local documentation on >> how to manipulate these messages. >> >> >> Below is the data which will enable a MIME compliant mail reader >> implementation to automatically retrieve the ASCII version of the >> Internet-Draft. >> Content-Type: text/plain >> Content-ID: <2005-11-30114220.I-D@ietf.org> >> >> _______________________________________________ >> I-D-Announce mailing list >> I-D-Announce@ietf.org >> https://www1.ietf.org/mailman/listinfo/i-d-announce > > _______________________________________________ > Simple mailing list > Simple@ietf.org > https://www1.ietf.org/mailman/listinfo/simple _______________________________________________ Simple mailing list Simple@ietf.org https://www1.ietf.org/mailman/listinfo/simple From simple-bounces@ietf.org Wed Dec 07 01:44:54 2005 Received: from localhost.cnri.reston.va.us ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1Ejt2s-0001qC-OU; Wed, 07 Dec 2005 01:44:54 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1Ejt2r-0001oG-AT for simple@megatron.ietf.org; Wed, 07 Dec 2005 01:44:53 -0500 Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id BAA20617 for ; Wed, 7 Dec 2005 01:44:01 -0500 (EST) Received: from mgw-ext01.nokia.com ([131.228.20.93]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1EjtOU-00030F-Cv for simple@ietf.org; Wed, 07 Dec 2005 02:07:15 -0500 Received: from esebh106.NOE.Nokia.com (esebh106.ntc.nokia.com [172.21.138.213]) by mgw-ext01.nokia.com (Switch-3.1.7/Switch-3.1.7) with ESMTP id jB76igNF009739; Wed, 7 Dec 2005 08:44:43 +0200 Received: from esebh003.NOE.Nokia.com ([172.21.138.82]) by esebh106.NOE.Nokia.com with Microsoft SMTPSVC(6.0.3790.1830); Wed, 7 Dec 2005 08:44:12 +0200 Received: from mgw-int2.ntc.nokia.com ([172.21.143.97]) by esebh003.NOE.Nokia.com with Microsoft SMTPSVC(5.0.2195.6881); Wed, 7 Dec 2005 08:44:12 +0200 Received: from kusti.research.nokia.com (mgw.research.nokia.com [172.21.56.13]) by mgw-int2.ntc.nokia.com (Switch-2.2.8/Switch-2.2.8) with ESMTP id jB76i6525557; Wed, 7 Dec 2005 08:44:06 +0200 (EET) Received: from xitami.research.nokia.com (xitami.research.nokia.com [172.21.50.105]) by kusti.research.nokia.com (Postfix) with ESMTP id 714D093B7A; Wed, 7 Dec 2005 08:44:06 +0200 (EET) Received: from hed034-145.research.nokia.com (hed034-145.research.nokia.com [172.21.34.145]) by xitami.research.nokia.com (Postfix) with ESMTP id 589472E3; Wed, 7 Dec 2005 08:44:06 +0200 (EET) Subject: Re: [Simple] draft-ietf-simple-xml-patch-ops-00 From: Jari Urpalainen To: ext Cullen Jennings In-Reply-To: References: Content-Type: text/plain Date: Wed, 07 Dec 2005 08:44:05 +0200 Message-Id: <1133937845.21359.26.camel@hed034-145.research.nokia.com> Mime-Version: 1.0 X-Mailer: Evolution 2.2.3 (2.2.3-2.fc4) Content-Transfer-Encoding: 7bit X-OriginalArrivalTime: 07 Dec 2005 06:44:12.0028 (UTC) FILETIME=[A1EB4BC0:01C5FAF9] X-Spam-Score: 0.0 (/) X-Scan-Signature: b19722fc8d3865b147c75ae2495625f2 Content-Transfer-Encoding: 7bit Cc: "simple@ietf.org" X-BeenThere: simple@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: SIP for Instant Messaging and Presence Leveraging Extensions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: simple-bounces@ietf.org Errors-To: simple-bounces@ietf.org On Mon, 2005-12-05 at 21:17 -0800, ext Cullen Jennings wrote: > I was somewhat surprised to see this as a WG item. When do we use this and > when do we use xcap? Robert answered to this. > I was also sort of wondering about how to deal with the issues of elements > that used name spaces inside of the data portion of attributes. For > example... > > if I have namesace xmlns:z="urn:foo" > > then I have sel="z:doc" > > Would I ever have the case where the some xml parser library changed my > namespace to xmlns:z="urn:foo" (it would do this perhaps because x was > already in use)? If this happened, it seems like the "z:doc" would not get > changed to "x:doc" and things would break badly. > > Thoughts? Is this a problem or is it all avoided some how? > I had some trouble in understanding the issue, but you can add or change namespace prefixes of some elements when you use local namespace declarations within them, as an example: . However, I cannot imagine a real use case for it. In patch-ops the namespaces within the "body" are changed to to use the declarations within the initial document and matching is based on local-names and namespace URIs, so a similar model is adopted what XPath uses when locating nodes. br, Jari _______________________________________________ Simple mailing list Simple@ietf.org https://www1.ietf.org/mailman/listinfo/simple From simple-bounces@ietf.org Wed Dec 07 02:14:19 2005 Received: from localhost.cnri.reston.va.us ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1EjtVL-000122-LS; Wed, 07 Dec 2005 02:14:19 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1EjtVJ-00011x-Jy for simple@megatron.ietf.org; Wed, 07 Dec 2005 02:14:17 -0500 Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id CAA23811 for ; Wed, 7 Dec 2005 02:13:21 -0500 (EST) Received: from mgw-ext03.nokia.com ([131.228.20.95]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1Ejtqo-0003za-2A for simple@ietf.org; Wed, 07 Dec 2005 02:36:32 -0500 Received: from esebh106.NOE.Nokia.com (esebh106.ntc.nokia.com [172.21.138.213]) by mgw-ext03.nokia.com (Switch-3.1.7/Switch-3.1.7) with ESMTP id jB77AZ0M019590; Wed, 7 Dec 2005 09:10:37 +0200 Received: from esebh003.NOE.Nokia.com ([172.21.138.82]) by esebh106.NOE.Nokia.com with Microsoft SMTPSVC(6.0.3790.1830); Wed, 7 Dec 2005 09:13:03 +0200 Received: from mgw-int2.ntc.nokia.com ([172.21.143.97]) by esebh003.NOE.Nokia.com with Microsoft SMTPSVC(5.0.2195.6881); Wed, 7 Dec 2005 09:13:03 +0200 Received: from kusti.research.nokia.com (mgw.research.nokia.com [172.21.56.13]) by mgw-int2.ntc.nokia.com (Switch-2.2.8/Switch-2.2.8) with ESMTP id jB77Cu504625; Wed, 7 Dec 2005 09:12:56 +0200 (EET) Received: from xitami.research.nokia.com (xitami.research.nokia.com [172.21.50.105]) by kusti.research.nokia.com (Postfix) with ESMTP id 088EC93B78; Wed, 7 Dec 2005 09:12:56 +0200 (EET) Received: from hed034-145.research.nokia.com (hed034-145.research.nokia.com [172.21.34.145]) by xitami.research.nokia.com (Postfix) with ESMTP id F32B22E3; Wed, 7 Dec 2005 09:12:55 +0200 (EET) Subject: Re: [Simple] draft-ietf-simple-xml-patch-ops-00 From: Jari Urpalainen To: ext Robert Sparks In-Reply-To: References:

Content-Type: text/plain Date: Wed, 07 Dec 2005 09:12:55 +0200 Message-Id: <1133939575.21359.53.camel@hed034-145.research.nokia.com> Mime-Version: 1.0 X-Mailer: Evolution 2.2.3 (2.2.3-2.fc4) Content-Transfer-Encoding: 7bit X-OriginalArrivalTime: 07 Dec 2005 07:13:03.0155 (UTC) FILETIME=[A9C05030:01C5FAFD] X-Spam-Score: 0.0 (/) X-Scan-Signature: 7aafa0432175920a4b3e118e16c5cb64 Content-Transfer-Encoding: 7bit Cc: Cullen Jennings , "simple@ietf.org" X-BeenThere: simple@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: SIP for Instant Messaging and Presence Leveraging Extensions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: simple-bounces@ietf.org Errors-To: simple-bounces@ietf.org On Tue, 2005-12-06 at 15:27 -0600, ext Robert Sparks wrote: > On Dec 5, 2005, at 11:17 PM, Cullen Jennings wrote: > > > > > I was somewhat surprised to see this as a WG item. When do we use > > this and > > when do we use xcap? > > This draft is intended to be what the group agreed to adopt as the > solution for > xcap-diff and the partial-* work based on the output of the patch bof > and the > SIMPLE WG discussion in Vancouver. It went beyond its mandate > including patch > operations for general text elements - this is something the group > explicitly decided > to not try to tackle by my memory. > > I can see your confusion given that the draft doesn't reference > partial at all. > Partial pidf format is referenced and it is also mentioned in the text, isn't that enough ? > Jari - could you provide a revision quicky that includes a section > pointing to how this > would be used with xcap and with partial? > reference to xcap-diff could be added, but I didn't do it as there isn't yet a xcap-diff spec that references patch-ops. > All - comment on the text modifying proposal quickly. Unless there is > a very > strong "Oh yeah - we all want to do this this way", and soon, I will > ask Jari to remove > this mechanism from this draft and return to exactly the scope we > agreed to > in Vancouver. > > RjS > Agreed, those with a "desperate" need for this should speak up. This is certainly feature creep that doesn't fit to the spec very well. Also, I don't like reinventing the wheel unless absolutely necessary, but I don't feel comfortable with the ipr issue of vcdiff. If that doesn't vanish I'll intend to remove text-patching from the spec. vcdiff and gdiff have "copy & add" logic, so in order to differentiate one could propose a "add & replace" logic like:

New text inserted after char-pos 44100removed three chars from pos 100 and added this text. But as said this is still reinventing and as partial-pidf or xcap-diff do not need this (though text-patching is a separate operation) it should not be in this spec. thanks, Jari _______________________________________________ Simple mailing list Simple@ietf.org https://www1.ietf.org/mailman/listinfo/simple From simple-bounces@ietf.org Wed Dec 07 03:34:48 2005 Received: from localhost.cnri.reston.va.us ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1EjulE-0003g1-Jh; Wed, 07 Dec 2005 03:34:48 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1EjulC-0003fY-KA for simple@megatron.ietf.org; Wed, 07 Dec 2005 03:34:46 -0500 Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id DAA01587 for ; Wed, 7 Dec 2005 03:33:54 -0500 (EST) Received: from magus.nostrum.com ([69.5.195.2] helo=nostrum.com ident=root) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1Ejv6q-0006J5-Vy for simple@ietf.org; Wed, 07 Dec 2005 03:57:10 -0500 Received: from [131.106.56.194] (ip-66-181-12-21.cust.i2bnetworks.com [66.181.12.21]) (authenticated bits=0) by nostrum.com (8.12.11/8.12.11) with ESMTP id jB78YJ3T011752 (version=TLSv1/SSLv3 cipher=RC4-SHA bits=128 verify=NO); Wed, 7 Dec 2005 02:34:21 -0600 (CST) (envelope-from rjsparks@nostrum.com) In-Reply-To: <1133939575.21359.53.camel@hed034-145.research.nokia.com> References:

<1133939575.21359.53.camel@hed034-145.research.nokia.com> Mime-Version: 1.0 (Apple Message framework v746.2) Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed Message-Id: <86555A6D-CFB0-4595-8FE6-069F768F640A@nostrum.com> Content-Transfer-Encoding: 7bit From: Robert Sparks Subject: Re: [Simple] draft-ietf-simple-xml-patch-ops-00 Date: Wed, 7 Dec 2005 00:32:18 -0800 To: Jari Urpalainen X-Mailer: Apple Mail (2.746.2) Received-SPF: pass (nostrum.com: 66.181.12.21 is authenticated by a trusted mechanism) X-Spam-Score: 0.0 (/) X-Scan-Signature: de4f315c9369b71d7dd5909b42224370 Content-Transfer-Encoding: 7bit Cc: Cullen Jennings , "simple@ietf.org" X-BeenThere: simple@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: SIP for Instant Messaging and Presence Leveraging Extensions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: simple-bounces@ietf.org Errors-To: simple-bounces@ietf.org On Dec 6, 2005, at 11:12 PM, Jari Urpalainen wrote: > On Tue, 2005-12-06 at 15:27 -0600, ext Robert Sparks wrote: >> I can see your confusion given that the draft doesn't reference >> partial at all. >> > Partial pidf format is referenced and it is also mentioned in the > text, > isn't that enough ? I meant to say xcap there. Sorry for the confusion. I do think more text pointing to the uses would be helpful. I'll try to pull something together to contribute. RjS _______________________________________________ Simple mailing list Simple@ietf.org https://www1.ietf.org/mailman/listinfo/simple From simple-bounces@ietf.org Thu Dec 08 07:46:46 2005 Received: from localhost.cnri.reston.va.us ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1EkLAc-0000eL-H1; Thu, 08 Dec 2005 07:46:46 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1EkLA2-0000dB-0H for simple@megatron.ietf.org; Thu, 08 Dec 2005 07:46:30 -0500 Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA09266 for ; Thu, 8 Dec 2005 07:45:09 -0500 (EST) Received: from mailgw3.ericsson.se ([193.180.251.60]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1EkLVi-0006oe-S2 for simple@ietf.org; Thu, 08 Dec 2005 08:08:40 -0500 Received: from esealmw129.eemea.ericsson.se (unknown [153.88.254.120]) by mailgw3.ericsson.se (Symantec Mail Security) with ESMTP id CB0061198; Thu, 8 Dec 2005 13:45:50 +0100 (CET) Received: from esealmw127.eemea.ericsson.se ([153.88.254.171]) by esealmw129.eemea.ericsson.se with Microsoft SMTPSVC(6.0.3790.1830); Thu, 8 Dec 2005 13:44:25 +0100 Received: from mail.lmf.ericsson.se ([131.160.11.50]) by esealmw127.eemea.ericsson.se with Microsoft SMTPSVC(6.0.3790.1830); Thu, 8 Dec 2005 13:44:24 +0100 Received: from nomadiclab.lmf.ericsson.se (nomadiclab.lmf.ericsson.se [131.160.33.3]) by mail.lmf.ericsson.se (Postfix) with ESMTP id AC124236D; Thu, 8 Dec 2005 14:44:24 +0200 (EET) Received: from localhost.localdomain (localhost [127.0.0.1]) by nomadiclab.lmf.ericsson.se (Postfix) with ESMTP id 728E01AB8EE; Thu, 8 Dec 2005 14:44:24 +0200 (EET) From: "Salvatore Loreto (JO/LMF)" To: simple@ietf.org In-Reply-To: <1134021749.3365.4.camel@n121.nomadiclab.com> References: <1134021749.3365.4.camel@n121.nomadiclab.com> Content-Type: text/plain Date: Thu, 08 Dec 2005 14:44:24 +0200 Message-Id: <1134045864.3349.4.camel@w189.nomadiclab.com> Mime-Version: 1.0 X-Mailer: Evolution 2.2.3 (2.2.3-2.fc4) Content-Transfer-Encoding: 7bit X-OriginalArrivalTime: 08 Dec 2005 12:44:24.0958 (UTC) FILETIME=[1EA471E0:01C5FBF5] X-Brightmail-Tracker: AAAAAA== X-Spam-Score: 0.0 (/) X-Scan-Signature: 68c8cc8a64a9d0402e43b8eee9fc4199 Content-Transfer-Encoding: 7bit Cc: RjS@estacado.net Subject: [Simple] simple-xcap in rfc editor queue X-BeenThere: simple@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: SIP for Instant Messaging and Presence Leveraging Extensions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: simple-bounces@ietf.org Errors-To: simple-bounces@ietf.org Hi all, I've just checked and the draft draft-ietf-simple-xcap is still in RFC-Editor's Queue. When it'll be removed? Or in other way what is the right process, or the process does the wg want follow in this case? thank you Sal _______________________________________________ Simple mailing list Simple@ietf.org https://www1.ietf.org/mailman/listinfo/simple From simple-bounces@ietf.org Fri Dec 09 04:27:41 2005 Received: from localhost.cnri.reston.va.us ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1EkeXV-0000Pl-3c; Fri, 09 Dec 2005 04:27:41 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1EkeXS-0000P8-9J for simple@megatron.ietf.org; Fri, 09 Dec 2005 04:27:39 -0500 Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA06725 for ; Fri, 9 Dec 2005 04:26:40 -0500 (EST) Resent-From: ashutosh_p@spanservices.com Resent-Message-Id: <200512090926.EAA06725@ietf.org> Received: from [202.177.174.130] (helo=spanservices.com) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1EkeXV-0003rP-AD for simple@ietf.org; Fri, 09 Dec 2005 04:27:43 -0500 Received: from [202.177.174.131] (HELO Maya) by spanservices.com (MicroWorld SMTP 5.6.2) ; Fri, 09 Dec 2005 14:57:06 +0530 Resent-Date: Fri, 09 Dec 2005 14:57:06 +0530 X-Originating-IP: 202.177.174.131 X-Auth-User: ashutosh_p@spanservices.com X-Filename: C:\PROGRA~1\MAILSCAN\in\SMT1522471478208.TMP X-MSReally-From: ashutosh_p@spanservices.com From: "Ashutosh P - SPAN" To: Date: Fri, 9 Dec 2005 14:57:03 +0530 Message-ID: MIME-Version: 1.0 X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook IMO, Build 9.0.2416 (9.0.2911.0) X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1165 Importance: Normal X-Spam-Score: 1.2 (+) X-Scan-Signature: 10d2fdecab7a7fa796e06e001d026c91 Subject: [Simple] Help required in XCAP Server X-BeenThere: simple@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: SIP for Instant Messaging and Presence Leveraging Extensions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============1171086160==" Sender: simple-bounces@ietf.org Errors-To: simple-bounces@ietf.org --===============1171086160== Content-Type: multipart/related; boundary="----=_NextPart_000_0019_01C5FCD0.D0BAD730" ------=_NextPart_000_0019_01C5FCD0.D0BAD730 Content-Type: multipart/alternative; boundary="----=_NextPart_001_001A_01C5FCD0.D0BAD730" ------=_NextPart_001_001A_01C5FCD0.D0BAD730 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit HI, I am trying to understand and implement a simple XCAP server. But I dont know exactly where to start my reading. I have some fundaental knowledge about the Presence server and have undergone some RFC's and drafts in the simple link page. But I have some doubts regarding XCAP server. 1. How exactly I can relate an XCAP server to a SIP Presence Server? means how exactly they both are related? If someone could please give some pictorial architecture of the relation. 2. What all documents are required to go through for an XCAP server? 3. How the repository in XCAP server different from that of a Presence server? Any information on XCAP part will be of great help. Thanks & Regards, Ashutosh SPAN Systems Corporation, Bangalore. "Steering Progress, Together" -------------------------------------------------------------------------------- This email message and any attachments is confidential and intended only for the use of an individual or entity named above and may contain information that is privileged, confidential or exempt from disclosure under applicable law. If you are not the intended recipient, you are notified that any dissemination, distribution or copying of this email is strictly prohibited. If you have received this email in error, please notify us immediately by return email or itsupport@spanservices.com and destroy the original message. Opinions, conclusions, and other information in this message that do not relate to the official business of SPAN, shall be understood to be neither given nor endorsed by SPAN. ------=_NextPart_001_001A_01C5FCD0.D0BAD730 Content-Type: text/html; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable

HI,

I am = trying to=20 understand and implement a simple XCAP = server.

But I = dont know=20 exactly where to start my reading.

I have = some=20 fundaental knowledge about the Presence server

and have = undergone=20 some RFC's and drafts in the simple link page.

But I = have some=20 doubts regarding XCAP server.

1. How exactly I can relate an XCAP server to a SIP = Presence=20 Server?

means=20 how exactly they both are related?

= If someone=20 could please give some pictorial architecture of the=20 relation.

2. What = all=20 documents are required to go through for an XCAP = server?

=20

3. How = the=20 repository in XCAP server different from that of a Presence=20 server?

Any = information on=20 XCAP part will be of great help.

Thanks & = Regards,

= Ashutosh=20

SPAN Systems Corporation, Bangalore.
"Steering Progress, Together"

---------------------------------------------------------------------------= -----
This email message and any attachments is confidential and intended only = for the use of an individual or entity named above and may contain = information that is privileged, confidential or exempt from disclosure = under applicable law. If you are not the intended recipient, you are = notified that any dissemination, distribution or copying of this email is = strictly prohibited. If you have received this email in error, please = notify us immediately by return email or itsupport@spanservices.com and = destroy the original message. Opinions, conclusions, and other information = in this message that do not relate to the official business of SPAN, shall = be understood to be neither given nor endorsed by SPAN.

------=_NextPart_001_001A_01C5FCD0.D0BAD730-- ------=_NextPart_000_0019_01C5FCD0.D0BAD730 Content-Type: image/bmp; name="span logo.bmp" Content-Transfer-Encoding: base64 Content-ID: <812441209@09122005-088e> Content-Transfer-Encoding: base64 Qk2GHQAAAAAAADYEAAAoAAAAtAAAACQAAAABAAgAAAAAAFAZAAAAAAAAAAAAAAABAAAAAQAAXksk AGVNHgBqTh4AYkcfAGpRHgBtUh4AbFIcAGZTHgBxUx0AZk0hAGVNIwBpTSIAa04kAGNOKgBkUiwA alIhAGxTIQBtUiIAbVIlAG1UIgBuVSUAalMkAGxVKwBtWiwAaVYlAGVVMgBsVjIAbFs0AG1bOgBl WTsAcVYlAHFUIgBxVioAclklAHJZKgByWy0AcVszAHFdPABxVjEAc2I8AHZjOAByYTUATE5MAERG RQBPUU8AUlRSAF5eXQBaXFoAVllWAF5hXgBfYmEAalxBAG5hQQBhYV8AdGRDAHlqSQB4bVMAfnNW AGVmZQBjZGIAbW5tAGpsagBoaGYAbnFuAHJycQB1dXMAdnZ1AHN1cwB5eHYAenp5AHp9egB+f3wA fH17AHZ4dwBwcG8AfYB9AH6AgQCCajQAgXFNAIJ0VQCKe1wAh3dZAIl9ZACMgWoAgIB+AI2FcgCR hGUAmottAJqNcwCVinQAnJR7AJqRdACklnkAgoKBAISFgwCMjYwAh4iGAI6RjgCQkY8AnpaDAJOU kwCVmZYAm5ybAJiZlwCWj4UApJqEAK6kiQCmopkAsaaKALWrlAC3q5YAvLScALKwlwClpqUAoqOi AK6vrQCrrKoAqKmnALezqgCysrEAtre1ALO1swC6urkAvr69ALu9uwC3ubcArrGuAJ+goAC/wr8A wbaYAMW7pgDEvrAAyMKqAMLCvADOy7sAysW2ANLKswDTzLsA2cu4ANnSvQDCwsEAxcXDAMbGxQDC xcIAycnFAMrLyQDMzcsAxsnGANTNwgDV0sMA09LMANvVxADb1coA3tnFAN7aywDV1dMA09TTANvZ 1QDa29oA3d3bAN7f3QDb3NoA19nXAM/RzwDf4d4A4tvLAOHaxwDj3dQA6OXNAObi0wDh4d8A5ePc AOrk1ADt6twA7OfaAPHs3AD0898A4eLhAOTk4gDl5uQA4uXjAObp5gDt7OMA6erpAOrt6gDt7esA 7u/tAOvt7QDp6ecA7/LxAPPu4wDy7+oA9PHkAPHx7gD19OwA+fbrAP377AD69eUA8vLwAPHy8QDy 9fIA9fXzAPf39QD19/UA8/X1APT2+QD2+fYA9vn2APb58wD2+fkA9fv7APr39AD6+vIA+fn3APr6 9gD6/fYA/fvyAP369gD+/fIA/v32APr98QD4+fgA+Pv4APr6+AD7+/kA+vv5APv7+gD5+voA+fr8 APn8+QD4/PkA+vz5APr9+gD7/PoA+/77APv++gD5/foA+v38APz7+QD9+voA/Pz5APz8+gD9/fsA /Pz7AP7++gD8//wA/v78AP///QD+//4A////AP/+/gD9/f0A/fr9APv2+ADu8e4A3+HhAMrO3+Dg 7uDg4ODg4ODg4PHx8fHx8fHx8fHx8fHx8PP84e315PPg5dLR7e3s8uDq5+jo6Ojq6urq6urq6urq 6urq6urq6urq6ujo6PHx8fLy8urq6urq6urq6urq6urq6urq6urq6urq6urq6urq6urq6urq6urq 6urq6urq6urq6urq6ury8vLy8vHx8fHy8vHx8fHx8fHx8fHx8ejo6Orq6urq6urq6fHx8fHx8fHx 8fHx8s7f3+Dg7uDg4ODg4ODg4PHx8fHx8fHx8fHx8fHx6Ojy8tv09NPT9/ni6PLKv9bq6uXo6Ojq 6urq6urq6urq6urq6urq6urq6ujo6PHx8fLy8urq6urq6urq6urq6urq6urq6urq6urq6urq6urq 6urq6urq6urq6urq6urq6urq6urq6ury8vLy8vHx8fHy8vHx8fHx8fHx8fHx8ejo6Orq6urq6urq 6fHx8fHx8fHx8fHx8t7h4ODg7uDg4ODg4OHg4PHx8fHx8fHx8fDx6enp5efZxKlqTic2Tmql1NvZ woWQyPLo6Ofq6urq6urq6urq6urq6urq6urq6ujo6PHx8fLy8urq6urq6urq6urq6urq6urq6urq 6urq6urq6urq6urq6urq6urq6urq6urq6urq6urq6ury8vLy8vHx8fHy8vHx8fHx8fHx8fHx8ejo 6Orq6urq6urq6fHx8fHx8fHx8fHx8tbX39/i49nZ8Nfu4NXb2vT09/T099/n3tTc0Nfm3dnDWCQR EBQUESApVrDZ5PSGOIf08Ofy8vLy8u3y8vHx8fHq6urq6urq6ujo6Ojo6Ojo6Orq6urq8fHx8eDJ 3ujl6OXO9erq6urq6urq6urq6urq6M7lzujo6urq6uro6Ojx8fHx8fHx8fHx8fHx8fHx8fHx8fHx 8ere3ure5/Hy8vLy8fHx8fHx8fLx8fHx8fHx8fHx6dLS0dHd3dHR5ufw261SUVBQUFBQVavX0vCs U8PZ3r5QCg8RERARER4gG0/C89nbbg5cwOTz8/Py8vLy8vHx8fHq6urq6urq6ujo6Ojo6Ojo6Orq 6ujo6fHx4PLfopyizt7n6Orq6urq6urq6urq6urozqScosjq6urq6uro6Ojx8fHx8fHx8fHx8fHx 8fHx8fHx8fHx8erOoqK15/Hy8vHx8fHx8fHx8fLx8fHx8fHx8fHx8t/V2dfa2tvawKWJbjgOFhYa FhsdmtPu24s2NNrR21oMCB8PEBAQDxMhIiRv9NXfrygjTq3x4dLt8vTy8vLx4Onq5fXo6ufo5ejo 6Ojl6uje5eXq5ejo5+Dx8fKMYMmfZPjd6Oro6urq5erl6ufo6OrltEv+t2X46ure6uro3ujy8fHV 8fHx8vHx8fHx8fHg8vHx8fHf3/h+fP5zkeDx8d/g8+Li4vPf4unp8unh8eDx4N/g6dm/p5WDdmxj W1hXV1tbW1pjY1qL9N/XiyUWNq/Qig0FCAUJEBEQEB8UISJP2OnS1FEmF0+t193t6fDy8uDVqoCc 4+PLjrjosZOf3eikkaTOuMjl5bXLxrffxsGxYaCTMPXn6t633eXo5bjO3efLorTtu2T/sT3Husvn 58ihs97KqrPx1byk4ODGwfHx8eDgycng37qq3/WAk8ePZPbKsbrf4v6348vi3cvd6Le139XK39/+ 4dXV4PDW197ezt7l1tvZ2Nvb29vX4dapJRYWFQ5OKAoCAhECBgUTBgUVIiI2wOTk2lYXJzM5w9bt 6fDy8uC5QqJ3dPtyTLh7PaGAunhIsXnIZpHqzj3qe0DydXffLkNInOro58gquuXozju15bg9kWZ9 7T0uOnjoMLXoszp9ebSjeHJ7yWCMZ9VlYvfx8fHgXXjgkF2AQrixLDE7nrdKc3+x1TyRs0njk2L4 c2F5d/k7ubw1usrd3c7LztnT1dX09/f59/fy29bR3cNQDTRXXE8DCREFBQIJBgYGBgUSFCM2w/Dj w09QrrKnwtvx6erx8eDgxvf4Pflhd/hAo7y6+T2et737f6Pf1Unyjl3ydH35X35y3t7q5csqzvXl 4Ty343lh+b0u4mVmZr3dL7vyf3H5+fvyn0Re8slyOvHJyfHx8eDgXnz5Pbf5dXW6SHST+XJ6+fn2 x2D4t0DLjl7HL935+Pktud234dHR0czL0c3SzcJVUVBQUVFSqdff24M5lfT39fe+WhoPBQUEBgYF BgUTIRZY9NbnqCRXr9Tx4vzz8ery39/fungvYfVlce1GZnsunkNxfCqef3zx4ETxjTzidHq8K/l+ evXO5c4sfZO44zqe0Xlf+L0xxyrRoF/tL6DdcjxxQXOSL3fx1Sxis9/x8fHx8eDxXoD5PbX1fnGj Z/ktsX9JcTp0y2Dtuz3RkWC9K3JlMfUsteXl4dHe3tvaw6+lioEXFRYiIhpR1OfYwGjD29vi49/f 06xQCgUIEAQEEBMeIhua6ujaUCAjNm3a2/Lt8/Tx8eDKPmKx3r08P/+gTHFezJ5ecWT7cmJUyVT3 jEFkOrfjXnpLYt7d6MssuqQ9vUNfX9FFeGR7+11+ZEXMMl5ivUWMVLKeZHWc9mCMdPHx8fHx8eDy XpPnj1+RP7SxRZwqjrdMoz20jDyjui11SXf5Znp0cfkrRnTh6auWh3ZrY1lVU1NXWFlbV1mQ4/Da ldjn19nU29vu49XabBUEDxAPEBMeF1DU49htCh8eFhZZw+7k8/Tx8fHGPsrLoN50cuf16rn46PXe uvno3vfJ4KTy1fDGyfLi97X+yOjo6Mgqvbox/svo/vX1tLr16Pi0t/7lyM659t+gyfL2uqrV8d+e xuDy8vHx8dXVXYDO6rWiyOrouJu4ufP+m8nxsUW7uz//ovHf86Kh8d+8uaTf6djU2NjY2NXKy83N y9DU1NDj4/DZudPW3tSsmaXAxNvW2IgZEQ8PERQWGabz24oODwYQFSEjbPTk7fTx8fHfqmJfkeXh y+jq6ujo6Ojo6Orq6vHx30fV3/Hx8fHx6Ojo6Ojo5ctfZ1+R6Oro6urq6Ojo6urq6Oro6Ojg4PLx 8fHx8fHx8fHy4PHy8vHx8ZFFQks/s+Xo6ujl5erl3+Dx4ODx3brRt0rj3eDg4N/g4N/f8d/x6dXO 0dHRzc3d3tfX1+Pm3tbb1vDz5ODagk4WCxUkUW3A9NmIFQkSEh4Wb9v5lBYPEQYPDx4iHKnt5PHx 8eDg8vn49eje6Or16ujo6Ojo6Ovq6/Hx8fng8fHx8fHx8err6Ojo6On5+ff25d7q9eXq6urn6urq 6vXq6Ojy8fLx8fLx4PHx8fHy9uDy8vHx8fb5+fn55+fo6N7r6OXn5+Dx4PHx4uPox5zd8fHg4ODg 8eDg39/g6d/V1dXKy93TwJeZmJiZmb7X4dnb49BpDAwSDBISFhYagsLbiRwVFBZp3MSIGRAFEAQT DxQgF1ru0tfx8fLx8fHy8uDx8vbx8fHy8fHx4ODy4ODy4PHx8vLx8fLx8vbx8fHx8fHx8eDx6urq 6Ojn8vHy8uDx8fLx8fHy8fLx8eDx8fHy8fLy8fbx8fLx8fLy8vHx4PHx8fHx8fHx8fHg4ODg8fHg 8fHx8e7g4ODg4ODx4ODg6c7OztbU2NvEiA4mIyYkHJXj3vDb2ZkODAsLCQwLDxEUFk+l5IoWDmnT 2WoYBwQEBAQTEBMUIjjC4tfx8fHy8ff5+fn38vLy8vf39/Hy8fH29/fx8fHx4PL29/by9vf38fHx 8fHx8vfp6urq6Ojq8vL39/f28fLx8fHy9vb28uDx8fH29/f28vHx8fHx8vb28vHx8fLy8vb28vHy 8vLg4ODg4PLx8fHx8vHu8fH29vbx4ODg6b6rmpWHb2lVORkaGhobM6fV1+DZ2lYJCwsJCwsJDwIE Eg8bicSGa9qtVgMGBgIEAgIEBBMeITa+4Nfx8fHfm3JhXl9zouDgynp0gMrx4OCheXrK3/Hx8fGR eXy6oHiO4PHx8fHjjGTy6urq6OjooHlnZ3V7vPLx8fHgm3uMyfLxyY1zf3F9ofbx8uC5jY2q8fHy nI6OjYyMjcaejp7g4N/xt7Pg8eDBkpa6qo54eHueyfHg6cO+wL6+r62vr6+2travttPZ2+XRxA0P AQsLCwsLCwsMEiAUG4Lm45obBwIMAgQBAQQEDxARHja+8vTx8fbJR3Wyxrl3NWTx8nE+m/Hx8t/g dELx8eDx3/FfOp/KwUqO8fHx3d1iOkD46urq6Oj1X2abt6BkPYD28fHfkTpx4N/3jER6nqpzOl/K 4PHJSkDV4ODxejVIcnN0SHSzOpLy4N+5QGf24NXxRkb+RmSAnHdAQarp6crV1crK3crL0NDf4uHX 3uP02ufSqQAPCQsLCQsMBAQJEhIWWK7015UcCwQGBAQEBAQEBBMSIjfC5PPx8d/V3/fy4NX5Zy6S 33U1n+Dy4ODfukqA8vb297I8Z/LgwUGj8fHyvV81XkT56urq6OjVyffy8vb5Sjq84PHxnC558uDg svf58uD5fC548uDfQETg4N/fkDWO9/f2+brxQnjy8fdxPj2j8dXfMmW9vPb28vfKSkTG6ePd0c3R zc3Iq5WXmZimmMLi2N7NpQAKCQsLCwwMBxAMFhtv18Rti9qtNwkGBAoJCQIFEBAIFmnu7fHx8fbK 4N/ozv5zLz6g1XUunuDV39/g33RGj5ORkV88svHuyUCj6Of+XTySjUj38fHx8vHg3/Lg4Ml3NUHG 8fHKoy538d/f8d/g4NWqSDp74PHKSkT23+7ykD6N3+Df8fHVYmTg8aA+Z3RdyfGzMX7q3+Df38t4 O0nI6dXWytPU09bEhBkaJBscHabh197RxQAMCwsLCwsSEg8VNpfaxVcOJZfYrVIBBggFBAYFHyEi N77i6fDx8fHf8cp9Xjs6ZrHg4HUvoJ93ZIzg38tGZXx9ZDt49vHxxj+j3bRLSpvye0X38fHx8vHx 4MqOYko7Z6rx8fH3cS9Iyt/g4PaxdUU1RI3K8eDVQUXy8e72kDt/gHOg8fHxc1TVyl1AwbpBnPaM MaLo4PGcZT8xYqTO6cK5raeYhnZqUA4aJiMpHYfKy97h204JCwsSDAwSIA43rNi+UBUeICep28Np GggFBR8fIhc3mdri8/Dx8eDyoD8wS3rI6uHg338v//L2ezV39uV8Xs7oYUnH4vHxxj+btEM/oN/y fEf58fHx8vHgs0Q7XXrB9t/g8fKNLmJCZMrf33UuPWSi4Pbx1fbVQV3y8fHyjT5eZ2Gy1fHgjkDB kT564Pd6XeB/P7rosVQxQnW19d7d6cK/tq2urKiopqWprq6ttsL9yt/W24sNDBIMEhIgFzm/2cM5 DBAIHxQnmdfetm00AA4OGVy+29nf8eDx8d/JVCp8zurl5/Hx1X8vn+DfsjVF1eXLS4+jPnrz4vHx xkl0P0i48fH3fEX38vLy8fH2ZzWAxvHf4NXy4Jw6YcnBQH/5kTVHutXx8fLg1fHJQlT21eDxjT6Q 8fLf4PHgnz2gQkfK4ODGRXxdSPH5YC98y+ro5ejh8tbf1tbW1tzU0MrRzd3d3dXx59fZ49BYCgwS ICAgTr7d1FYPAgQGHiEeKYjU4PTarJSXw9vn4Nmr9ufx8fHfdSxms7i0k7zx32YvjKKjYDVz8uX1 kl5IXfv74vH2yEMxXbjd8eD3fUL28vLy8fHxdS5zuca5krnynz1Ewd/gszx0sTpUssrJoKOzn7e8 QUe5uaHKjTp6ubqhxuDxyj1dPaDx4ODgeEU8YuD3YTGTzt7Io87o8uHV3ePRzc3Ny8Kvr6+vrbbD 4e7b0s7EXCYWICAnrtTchAwfEQ8PExQQICRsxNnv4uHf49Hk2b6z6e3x8fHg4ZJdPz0/RrPpxl9J REVUZJvJ8971tWBenO378+DxkUtfyOjn8enJZEih8vLy8fHyynk/PTw9RLKgXl288dXpyWJBk5te PEBAP368QUdUREFCQkSdfzxAQUJBsvLxukBAZN/g4ODg4Ec+Z+HxumQ/QEU/PN3e8srV1c7V1dHN 06k0HCcoJzRj2OLi4Ofl3IdQIxlv8OLaTg8SExAPDw8RICEUT4PZ9Obk/OzRvmnC4/Hq6urq6vX1 y73I3uXq5eXo6Ojq+PXo6PXo3d7l6urq6Orozujd6uXq6urd3uXL6urq6uro6PXO/re6yOjIzubq 6Ojo5cjIyOrl/rW1/t7h/srJycnJycnJwcnJycnG4PLgysbJyvLx8fHx8snBwd/x8ffGsZ+yut/g 6N7Qwr+2rayZhGopFxokJho2r9fW4OL80eTaN0/Z29asABMRDwQPEA8EBR8hIhgnbKiwwL+mOJX1 +/Lq6urq6urq6Ojq9ejo9erq6vXl6urq6urq6vXo6Orq6urq5ejl5c646Or16uX16urq6urq6vXo 5+rq6Orl6urq6urq5eXo3ujo6Oro5eXd5fLg8fHy8fHg4PHg4PHg8vL28fLy8fLx8fHx4ODy4PLg 8fHy8fHg4N/h6M61n5qVlIeFhYeGiYaJiYmUtu/f4NSDhKWKG4Hk8NttAQUREw8PEA8QEBMfISEf EBQjTSgkadvt+/Lq6urq6urq6urq6urq6Orq6urq6urq6urq6urq6urq6urq6urq6uro6urq6urq 6urq6urq6ujq6urq6urq6urq6urq6urq6Ojq6urq6urq6vHx8fHx8fHx4PHx8fHx8fHx8fHx8fLy 8fHx8fHg4PHx8fHx8fHx8fHp6N7X29fa2+/v79nv7tfX69fb2/TV4NqGHRYkJKbS1fRqAQUREw8E EBQQEhIeIiBqbVYXIRdPwOP28vvq6urq6urq6urq6urq6urq6urq6urq6urq6urq6urq6urq6urq 6urq6urq6urq6urq6urq6urq6urq6urq6urq6urq6urq6urq6urq6urq6vHx8fHx8fHx8fHx8fHx 8fHx8fHx8fLy8fHx8fHx4PHx8fHx8fHx8fHy6t/f4N7j493h39bfwqWmpaWlpZrD3+/ZghsjJafc 6fSEARAMEBAQBA8RERMUKSWt174nI1HA0tHb29Lq6urq6urq6urq6urq6urq6urq6urq6urq6urq 6urq6urq6urq6urq6urq6urq6urq6urq6urq6urq6urq6urq6urq6urq6urq6urq6urq6vHx8fHy 8vLy8vHx8fHx8fHx8fHx8fLy8fHx8vLy8fLy8fHx8fHx8fHy9dXw1tbW4OTk+/r3xDkODQ0ODg5S xdbR8G0kJYfX4+7FGxEIDxAFBRERFCEhGW/01q0bUq717ezy6u3q6urq6urq6urq6urq6urq6urq 6urq6urq6urq6urq6urq6urq6urq6urq6urq6urq6urq6urq6urq6urq6urq6urq6urq6urq6urq 6urq6urq6urq6urq6urq6urq6urq6urq6ujo6Ojo6ujo6Ojo6urq6urq6urq6PHV8NXWwrCahHBa UTQZFxcbJSUzU9jWytqCM1Pa/OTbbwoTBBEFCAUeFCMkWNrX1adaxO716urq6urq6urq6urq6urq 6urq6urq6urq6urq6urq6urq6urq6urq6urq6urq6urq6urq6urq6urq6urq6urq6urq6urq6urq 6urq6urq6urq6urq6urq6urq6urq6urq6urq6urq6urq6ujo6Ojo6Ojo6Ojo6urq6urq6urq6ODg 1byqnZaWo5iYmJiampqlmqaamL/Z4+Hbp1Jt2/v8wmwODxERHh4iFhxqw9fQ59Xb19Lq6urq6urq 6urq6urq6urq6urq6urq6urq6urq6urq6Orq6urq6urq6urq6urq6urq6urq6urq6urq6urq6urq 6urq6urq6urq6urq6urq6urq6urq6urq6urq6urq6urq6urq6urq6urq6ujo6Ojo6Ojo6Ojo6urq 6urq6urq6OLi4O7w8OLu4O7u4OHn5dLS0uXs7e3t7eTk4NqDhr/j/PSVVjcbHCdPaaz06ObX6Pz7 7e3q6urq6urq6urq6urq6urq6urq6urq6urq6urq6ujo6Orq6urq6urq6urq6urq6urq6urq6urq 6urq6urq6urq6urq6urq6urq6urq6urq6urq6urq6urq6urq6urq6urq6urq6urq6urq6urq6urq 6urq6urq6urq6urq6urq6uLi4u7u7u7g4uLi4dfX19fX3u3k6Ojn8vLq5fDXwrrW9OLy2MO+rr7D 2+Xs7Or78uvq9vTq6urq6urq6urq6urq6urq6urq6urq6urq6urq6ujq9erq6urq6urq6urq6urq 6urq6urq6urq6urq6urq6urq6urq6urq6urq6urq6urq6urq6urq6urq6urq6urq6urq6urq6urq 6urq6urq6urq6urq6urq6urq6urq6urq6vj4+Pj4+Pf3+Pr6+Pn5+fr6+vf39/f39/f3+Pj7+fn0 9vf4+Pj6+Pr4+Pj1+Pf59/f39/f4+Pj4+Pj4+Pj4+Pj4+Pj4+Pj4+Pj4+Pj4+Pj4+Pj4+Pj4+Pj4 +Pj4+Pj4+Pj4+Pj4+Pj4+Pj4+Pj4+Pj4+Pj4+Pj4+Pj4+Pj4+Pj4+Pj4+Pj4+Pj4+Pj4+Pj4+Pj4 +Pj4+Pj4+Pj4+Pj4+Pj4+Pj4+Pj4+Pj4+Pj4+Pj4+Pj4+A== ------=_NextPart_000_0019_01C5FCD0.D0BAD730-- --===============1171086160== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ Simple mailing list Simple@ietf.org https://www1.ietf.org/mailman/listinfo/simple --===============1171086160==-- From simple-bounces@ietf.org Fri Dec 09 10:42:01 2005 Received: from localhost.cnri.reston.va.us ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1EkkNl-00052c-EB; Fri, 09 Dec 2005 10:42:01 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1EkkNk-000521-NZ for simple@megatron.ietf.org; Fri, 09 Dec 2005 10:42:00 -0500 Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA20661 for ; Fri, 9 Dec 2005 10:41:07 -0500 (EST) Received: from mailgw3.ericsson.se ([193.180.251.60]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1EkkNn-0008Jd-BR for simple@ietf.org; Fri, 09 Dec 2005 10:42:14 -0500 Received: from esealmw129.eemea.ericsson.se (unknown [153.88.254.120]) by mailgw3.ericsson.se (Symantec Mail Security) with ESMTP id 32492F5B for ; Fri, 9 Dec 2005 16:41:37 +0100 (CET) Received: from esealmw127.eemea.ericsson.se ([153.88.254.171]) by esealmw129.eemea.ericsson.se with Microsoft SMTPSVC(6.0.3790.1830); Fri, 9 Dec 2005 16:41:20 +0100 Received: from esealmw105.eemea.ericsson.se ([153.88.200.68]) by esealmw127.eemea.ericsson.se with Microsoft SMTPSVC(6.0.3790.1830); Fri, 9 Dec 2005 16:41:20 +0100 Received: from 147.214.118.125 ([147.214.118.125]) by esealmw105.eemea.ericsson.se ([153.88.200.68]) via Exchange Front-End Server mail.eemea.ericsson.se ([153.88.254.169]) with Microsoft Exchange Server HTTP-DAV ; Fri, 9 Dec 2005 15:39:28 +0000 Received: from Caliope by mail.eemea.ericsson.se; 09 Dec 2005 16:41:18 +0100 From: Ignacio =?ISO-8859-1?Q?M=E1s?= "Ivars (KI/EAB)" To: simple@ietf.org Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Organization: Ericsson Research Date: Fri, 09 Dec 2005 16:41:18 +0100 Message-Id: <1134142878.4741.21.camel@localhost.localdomain> Mime-Version: 1.0 X-Mailer: Evolution 2.5.2 X-OriginalArrivalTime: 09 Dec 2005 15:41:20.0511 (UTC) FILETIME=[006B08F0:01C5FCD7] X-Brightmail-Tracker: AAAAAA== X-Spam-Score: 0.0 (/) X-Scan-Signature: 8abaac9e10c826e8252866cbe6766464 Content-Transfer-Encoding: quoted-printable Subject: [Simple] [MSRP v12] Interrupting a SEND of the *same* MSRP session X-BeenThere: simple@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: SIP for Instant Messaging and Presence Leveraging Extensions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: simple-bounces@ietf.org Errors-To: simple-bounces@ietf.org Hi all! Reading carefully the latest draft of MSRP we have some small doubts about the chunking mechanism. The draft says that any message over 2048 octects should be interruptible "to allow multiple MSRP sessions to share a TCP connection, and for large messages to be sent efficiently while not blocking other messages that share the same connection." I understand the previous paragraph in the following way: one MSRP session starts sending a large file and another MSRP session using the same TCP connection is able to interrupt the SEND and interleave its messages... but what if we have *one* single MSRP session, we start to send a large file and we want to interleave a text message? Can the MSRP session that started the file send interrupt itself to send another message and then continue? This is the way I interpret it, but I would like a confirmation from the group. It could be good to clarify the paragraph, perhaps adding "...while not blocking other messages that share the same connection, or even the same MSRP session"... Thanks for the help! /Ignacio --=20 Ignacio M=E1s Ivars Service enablers and protocols, Ericsson Research (EAB/TBG/B) Ericsson AB Phone: +46 8 4045580 Torshamsgatan 23 Fax: +46 8 4049500 SE-164 80 Stockholm, Sweden mailto: ignacio.mas.ivars@ericsson.com _______________________________________________ Simple mailing list Simple@ietf.org https://www1.ietf.org/mailman/listinfo/simple From simple-bounces@ietf.org Mon Dec 12 13:03:12 2005 Received: from localhost.cnri.reston.va.us ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1Els12-0001Yw-C6; Mon, 12 Dec 2005 13:03:12 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1Els0z-0001YB-AD for simple@megatron.ietf.org; Mon, 12 Dec 2005 13:03:10 -0500 Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA24416 for ; Mon, 12 Dec 2005 13:02:05 -0500 (EST) Received: from sj-iport-4.cisco.com ([171.68.10.86]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1Els1g-0005Pe-Ih for simple@ietf.org; Mon, 12 Dec 2005 13:03:53 -0500 Received: from sj-core-3.cisco.com ([171.68.223.137]) by sj-iport-4.cisco.com with ESMTP; 12 Dec 2005 10:02:51 -0800 Received: from vtg-um-e2k4.sj21ad.cisco.com (vtg-um-e2k4.cisco.com [171.70.93.57]) by sj-core-3.cisco.com (8.12.10/8.12.6) with ESMTP id jBCI2mMe018906; Mon, 12 Dec 2005 10:02:49 -0800 (PST) Received: from 10.21.89.0 ([10.21.89.0]) by vtg-um-e2k4.sj21ad.cisco.com ([171.70.93.57]) with Microsoft Exchange Server HTTP-DAV ; Mon, 12 Dec 2005 18:02:48 +0000 User-Agent: Microsoft-Entourage/11.2.1.051004 Date: Mon, 12 Dec 2005 10:02:55 -0800 Subject: Re: [Simple] [MSRP v12] Interrupting a SEND of the *same* MSRP session From: Cullen Jennings To: "Ivars (KI/EAB) Ignacio M=?ISO-8859-1?B?4Q==?=s" , "simple@ietf.org" Message-ID: Thread-Topic: [Simple] [MSRP v12] Interrupting a SEND of the *same* MSRP session Thread-Index: AcX/RkbEhZyizms5EdqiaQARJEEJ/A== In-Reply-To: <1134142878.4741.21.camel@localhost.localdomain> Mime-version: 1.0 Content-type: text/plain; charset="ISO-8859-1" Content-transfer-encoding: quoted-printable X-Spam-Score: 0.0 (/) X-Scan-Signature: 52e1467c2184c31006318542db5614d5 Content-Transfer-Encoding: quoted-printable Cc: X-BeenThere: simple@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: SIP for Instant Messaging and Presence Leveraging Extensions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: simple-bounces@ietf.org Errors-To: simple-bounces@ietf.org On 12/9/05 7:41 AM, "Ivars (KI/EAB) Ignacio M=E1s" wrote: >=20 > Hi all! >=20 > Reading carefully the latest draft of MSRP we have some small doubts > about the chunking mechanism. The draft says that any message over 2048 > octects should be interruptible "to allow multiple MSRP sessions to > share a TCP connection, and for large messages to be sent efficiently > while not blocking other messages that share the same connection." >=20 > I understand the previous paragraph in the following way: one MSRP > session starts sending a large file and another MSRP session using the > same TCP connection is able to interrupt the SEND and interleave its > messages... but what if we have *one* single MSRP session, we start to > send a large file and we want to interleave a text message? Can the MSRP > session that started the file send interrupt itself to send another > message and then continue? This is the way I interpret it, but I would > like a confirmation from the group. yes - your understanding is correct. >=20 > It could be good to clarify the paragraph, perhaps adding "...while not > blocking other messages that share the same connection, or even the same > MSRP session"... Sounds good - I made this change and the net version will have it. Thanks. >=20 > Thanks for the help! > /Ignacio >=20 _______________________________________________ Simple mailing list Simple@ietf.org https://www1.ietf.org/mailman/listinfo/simple From simple-bounces@ietf.org Mon Dec 12 13:09:13 2005 Received: from localhost.cnri.reston.va.us ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1Els6r-0002sd-GP; Mon, 12 Dec 2005 13:09:13 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1Els6p-0002s2-H6 for simple@megatron.ietf.org; Mon, 12 Dec 2005 13:09:11 -0500 Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA25017 for ; Mon, 12 Dec 2005 13:08:15 -0500 (EST) Received: from sj-iport-5.cisco.com ([171.68.10.87]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1Els7e-0005b1-QW for simple@ietf.org; Mon, 12 Dec 2005 13:10:04 -0500 Received: from sj-core-3.cisco.com ([171.68.223.137]) by sj-iport-5.cisco.com with ESMTP; 12 Dec 2005 10:09:01 -0800 X-IronPort-AV: i="3.99,244,1131350400"; d="scan'208"; a="240052678:sNHT30953984" Received: from vtg-um-e2k4.sj21ad.cisco.com (vtg-um-e2k4.cisco.com [171.70.93.57]) by sj-core-3.cisco.com (8.12.10/8.12.6) with ESMTP id jBCI8wMe020506; Mon, 12 Dec 2005 10:08:59 -0800 (PST) Received: from 10.21.89.0 ([10.21.89.0]) by vtg-um-e2k4.sj21ad.cisco.com ([171.70.93.57]) with Microsoft Exchange Server HTTP-DAV ; Mon, 12 Dec 2005 18:08:58 +0000 User-Agent: Microsoft-Entourage/11.2.1.051004 Date: Mon, 12 Dec 2005 10:09:06 -0800 Subject: Re: [Simple] IMDN Issue #1: Security of IMDN From: Cullen Jennings To: Eric Burger , "simple@ietf.org" Message-ID: Thread-Topic: [Simple] IMDN Issue #1: Security of IMDN Thread-Index: AcX5ygqNRz99IFFbS4ezLwACE5TCZgFfRlYm In-Reply-To: <330A23D8336C0346B5C1A5BB1966664701B8D4E8@ATLANTIS.Brooktrout.com> Mime-version: 1.0 Content-type: text/plain; charset="US-ASCII" Content-transfer-encoding: 7bit X-Spam-Score: 0.0 (/) X-Scan-Signature: 0bc60ec82efc80c84b8d02f4b0e4de22 Content-Transfer-Encoding: 7bit Cc: X-BeenThere: simple@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: SIP for Instant Messaging and Presence Leveraging Extensions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: simple-bounces@ietf.org Errors-To: simple-bounces@ietf.org On 12/5/05 10:31 AM, "Burger, Eric" wrote: > Proposal is that if the body of the message was encrypted or signed, the > IMDN MUST be encrypted or signed, otherwise it MAY be plain text. > > Any dissent? If the IMDN was only signed, but the original message was encrypted, would the IMDN reveal anything that was not in the unencrypted portion of the message? This proposal does seem a little weird - what happens if you can't sign the IMDN? Perhaps we might want something like the following 3 rules Always sign the IMDN if you have a cert. If the message was singed and encrypted, MUST encrypt repose. If the message was encrypted, MUST sign IMDN. _______________________________________________ Simple mailing list Simple@ietf.org https://www1.ietf.org/mailman/listinfo/simple From simple-bounces@ietf.org Mon Dec 12 13:28:21 2005 Received: from localhost.cnri.reston.va.us ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1ElsPN-0007kU-KJ; Mon, 12 Dec 2005 13:28:21 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1ElsPM-0007jO-1h for simple@megatron.ietf.org; Mon, 12 Dec 2005 13:28:20 -0500 Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA27548 for ; Mon, 12 Dec 2005 13:27:24 -0500 (EST) Received: from sj-iport-5.cisco.com ([171.68.10.87]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1ElsQB-0006Ji-DK for simple@ietf.org; Mon, 12 Dec 2005 13:29:12 -0500 Received: from sj-core-4.cisco.com ([171.68.223.138]) by sj-iport-5.cisco.com with ESMTP; 12 Dec 2005 10:28:10 -0800 X-IronPort-AV: i="3.99,244,1131350400"; d="scan'208"; a="240057604:sNHT1111519396" Received: from vtg-um-e2k4.sj21ad.cisco.com (vtg-um-e2k4.cisco.com [171.70.93.57]) by sj-core-4.cisco.com (8.12.10/8.12.6) with ESMTP id jBCIS4ph013282; Mon, 12 Dec 2005 10:28:07 -0800 (PST) Received: from 10.21.89.0 ([10.21.89.0]) by vtg-um-e2k4.sj21ad.cisco.com ([171.70.93.57]) with Microsoft Exchange Server HTTP-DAV ; Mon, 12 Dec 2005 18:28:06 +0000 User-Agent: Microsoft-Entourage/11.2.1.051004 Date: Mon, 12 Dec 2005 10:28:14 -0800 From: Cullen Jennings To: Hisham Khartabil Message-ID: Thread-Topic: Addition to security section draft-ietf-simple-message-sessions Thread-Index: AcX/SdApDrxpYWs9EdqiaQARJEEJ/A== In-Reply-To: Mime-version: 1.0 Content-type: text/plain; charset="US-ASCII" Content-transfer-encoding: 7bit X-Spam-Score: 0.0 (/) X-Scan-Signature: 6d95a152022472c7d6cdf886a0424dc6 Content-Transfer-Encoding: 7bit Cc: "simple@ietf.org" Subject: [Simple] Re: Addition to security section draft-ietf-simple-message-sessions X-BeenThere: simple@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: SIP for Instant Messaging and Presence Leveraging Extensions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: simple-bounces@ietf.org Errors-To: simple-bounces@ietf.org Thanks - Made both theses changes in next version of document. On 11/28/05 1:44 AM, "Hisham Khartabil" wrote: > > On Nov 26, 2005, at 7:26 PM, Cullen Jennings wrote: > >> >> During a review of this draft by a security AD, we got feedback that we >> needed to add more about how to use TLS where there was no relays. I am >> proposing we add an additional section 14.3 with some proposed text >> below. >> If you want to see this in the context of the draft, you can look at >> what it >> might look like at: >> >> http://scm.sipfoundry.org/rep/ietf-drafts/simple/draft-ietf-simple- >> message-s >> essions.html >> >> http://scm.sipfoundry.org/rep/ietf-drafts/simple/draft-ietf-simple- >> message-s >> essions.txt >> >> The text I am proposing to add is .... >> >> 14.3. Using TLS in Peer to Peer Mode >> >> TLS can be used with a self signed certificate as long as there is a >> mechanism for both sides to ascertain that the other side used the >> correct >> certificate. When used with SDP and SIP, the correct certificate can >> be >> verified by passing a fingerprint of the certificate in the SDP and >> ensuring >> that the SDP has suitable integrity protection. When SIP is used to >> transport the SDP, the integrity can be provided by the SIP Identity >> mechanism. The rest of this section describes the details of this >> approach. >> >> If self-signed certificates are used, the content of the subjectAltName >> attribute inside the certificate MAY use the uniform resource >> identifier >> (URI) of the user. > > > Can you make it clear here that you are talking about the AoR? > >> This is useful for debugging purposes only and is not >> required to bind the certificate to one of the communication >> endpoints. The >> subjectAltName is not an important component of the certificate >> verification. If the endpoint is also able to make anonymous >> sessions, a >> distinct, unique certificate MUST be used for this purpose. For an >> client >> that works with multiple users, each user SHOULD have its own >> certificate. >> The generation of public/private key pairs is relatively expensive. >> Endpoints are not required to generate certificates for each session. >> >> A certificate fingerprint is the output of a one-way hash function >> computed >> over the distinguished encoding rules (DER) form of the certificate. >> The >> endpoint MUST use the certificate fingerprint attribute as specified >> in [23] >> and MUST include this in the SDP. > > > A bit more text on how to include it in SDP would be good. Example > would be great. > > Thanks, > Hisham > >> The certificate presented during the TLS >> handshake needs to match the fingerprint exchanged via the SDP and if >> the >> fingerprint does not match the hashed certificate then the endpoint >> MUST >> tear down the media session immediately. >> >> When using SIP, the integrity of the fingerprint can be ensured >> through the >> SIP Identity mechanism [22]. When a client wishes to use SIP to set >> up a >> secure MSRP session with another endpoint it sends an offer in a SIP >> message >> to the other endpoint. This offer includes, as part of the SDP >> payload, the >> fingerprint of the certificate that the endpoint wants to use. The SIP >> message containing the offer is sent to the offerer's sip proxy which >> will >> add an identity header according to the procedures outlined in [22]. >> When >> the far endpoint receives the SIP message it can verify the identity >> of the >> sender using the identity header. Since the identity header is a >> digital >> signature across several SIP headers, in addition to the body or >> bodies of >> the SIP message, the receiver can also be certain that the message has >> not >> been tampered with after the digital signature was added to the SIP >> message. >> _______________________________________________ Simple mailing list Simple@ietf.org https://www1.ietf.org/mailman/listinfo/simple From simple-bounces@ietf.org Mon Dec 12 18:50:54 2005 Received: from localhost.cnri.reston.va.us ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1ElxRW-00033b-7y; Mon, 12 Dec 2005 18:50:54 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1ElxRV-00033S-8L for simple@megatron.ietf.org; Mon, 12 Dec 2005 18:50:53 -0500 Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA15776 for ; Mon, 12 Dec 2005 18:49:41 -0500 (EST) Received: from mxgate1.brooktrout.com ([204.176.74.10]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1ElxS9-0003Zw-3V for simple@ietf.org; Mon, 12 Dec 2005 18:51:34 -0500 X-IronPort-AV: i="3.99,245,1131339600"; d="scan'208"; a="24073248:sNHT42891624" X-MimeOLE: Produced By Microsoft Exchange V6.5 Content-class: urn:content-classes:message MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable Subject: RE: [Simple] IMDN Issue #1: Security of IMDN Date: Mon, 12 Dec 2005 18:50:31 -0500 Message-ID: <330A23D8336C0346B5C1A5BB1966664701C7D74A@ATLANTIS.Brooktrout.com> Thread-Topic: [Simple] IMDN Issue #1: Security of IMDN Thread-Index: AcX5ygqNRz99IFFbS4ezLwACE5TCZgFfRlYmAAgUujA= From: "Burger, Eric" To: "Cullen Jennings" X-Spam-Score: 0.0 (/) X-Scan-Signature: a7d6aff76b15f3f56fcb94490e1052e4 Content-Transfer-Encoding: quoted-printable Cc: simple@ietf.org X-BeenThere: simple@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: SIP for Instant Messaging and Presence Leveraging Extensions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: simple-bounces@ietf.org Errors-To: simple-bounces@ietf.org How about: 1. If UAS has a certificate, MUST sign IMDN. 2. If message was encrypted, MUST encrypt IMDN. Doesn't encrypting cover signing? If not, to encrypt, need cert, so see rule 1. =20 -----Original Message----- From: Cullen Jennings [mailto:fluffy@cisco.com]=20 Sent: Monday, December 12, 2005 1:09 PM To: Burger, Eric; simple@ietf.org Subject: Re: [Simple] IMDN Issue #1: Security of IMDN On 12/5/05 10:31 AM, "Burger, Eric" wrote: > Proposal is that if the body of the message was encrypted or signed, the > IMDN MUST be encrypted or signed, otherwise it MAY be plain text. >=20 > Any dissent? If the IMDN was only signed, but the original message was encrypted, would the IMDN reveal anything that was not in the unencrypted portion of the message? This proposal does seem a little weird - what happens if you can't sign the IMDN? Perhaps we might want something like the following 3 rules Always sign the IMDN if you have a cert. If the message was singed and encrypted, MUST encrypt repose. If the message was encrypted, MUST sign IMDN. _______________________________________________ Simple mailing list Simple@ietf.org https://www1.ietf.org/mailman/listinfo/simple From simple-bounces@ietf.org Tue Dec 13 07:42:43 2005 Received: from localhost.cnri.reston.va.us ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1Em9UR-0002Q7-Pg; Tue, 13 Dec 2005 07:42:43 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1Em9UQ-0002P9-59 for simple@megatron.ietf.org; Tue, 13 Dec 2005 07:42:42 -0500 Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA17197 for ; Tue, 13 Dec 2005 07:41:45 -0500 (EST) Received: from mgw-ext03.nokia.com ([131.228.20.95]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1Em9VP-0006Xg-Hd for simple@ietf.org; Tue, 13 Dec 2005 07:43:44 -0500 Received: from esebh106.NOE.Nokia.com (esebh106.ntc.nokia.com [172.21.138.213]) by mgw-ext03.nokia.com (Switch-3.1.7/Switch-3.1.7) with ESMTP id jBDCcwXw027791; Tue, 13 Dec 2005 14:39:01 +0200 Received: from esebh001.NOE.Nokia.com ([172.21.138.28]) by esebh106.NOE.Nokia.com with Microsoft SMTPSVC(6.0.3790.1830); Tue, 13 Dec 2005 14:42:08 +0200 Received: from [10.162.253.176] ([10.162.253.176]) by esebh001.NOE.Nokia.com with Microsoft SMTPSVC(5.0.2195.6881); Tue, 13 Dec 2005 14:42:07 +0200 Message-ID: <439EC19E.2050504@nokia.com> Date: Tue, 13 Dec 2005 14:42:06 +0200 From: Aki Niemi User-Agent: Thunderbird 1.5 (X11/20051025) MIME-Version: 1.0 To: ext Cullen Jennings Subject: Re: [Simple] Re: Addition to security section draft-ietf-simple-message-sessions References: In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-OriginalArrivalTime: 13 Dec 2005 12:42:07.0920 (UTC) FILETIME=[A106DB00:01C5FFE2] X-Spam-Score: 0.0 (/) X-Scan-Signature: dbb8771284c7a36189745aa720dc20ab Content-Transfer-Encoding: 7bit Cc: "simple@ietf.org" X-BeenThere: simple@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: SIP for Instant Messaging and Presence Leveraging Extensions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: simple-bounces@ietf.org Errors-To: simple-bounces@ietf.org I took a look at the version with the added text. First of all, the fingerprint SDP attribute is not defined anywhere in the document. It should. Second, seems to me that sdescriptions would be the correct place to negotiate any security related data like the cert fingerprint in SDP; I don't understand why MSRP has to (again) invent its own mechanism. Then again, if the described mechanism works, I guess it is ok... Also, I'd like the text to at least mention, that there are other ciphersuites available in TLS that could potentially be used with MSRP. For example, ciphersuites defined in RFC 4279 come to mind as something worth exploring along with sdescriptions, or MIKEY perhaps. (This should be its own specification, though.) I can propose some text, too, if you'd like. Last (but not least), seems like e2e TLS is only possible when there are no relays, right? Then, doesn't that mean that NAT/FW traversal and e2e security don't work together? Doesn't that really suck, if you have to choose one or the other? Cheers, Aki ext Cullen Jennings wrote: > Thanks - Made both theses changes in next version of document. > > > On 11/28/05 1:44 AM, "Hisham Khartabil" wrote: > >> On Nov 26, 2005, at 7:26 PM, Cullen Jennings wrote: >> >>> During a review of this draft by a security AD, we got feedback that we >>> needed to add more about how to use TLS where there was no relays. I am >>> proposing we add an additional section 14.3 with some proposed text >>> below. >>> If you want to see this in the context of the draft, you can look at >>> what it >>> might look like at: >>> >>> http://scm.sipfoundry.org/rep/ietf-drafts/simple/draft-ietf-simple- >>> message-s >>> essions.html >>> >>> http://scm.sipfoundry.org/rep/ietf-drafts/simple/draft-ietf-simple- >>> message-s >>> essions.txt >>> >>> The text I am proposing to add is .... >>> >>> 14.3. Using TLS in Peer to Peer Mode >>> >>> TLS can be used with a self signed certificate as long as there is a >>> mechanism for both sides to ascertain that the other side used the >>> correct >>> certificate. When used with SDP and SIP, the correct certificate can >>> be >>> verified by passing a fingerprint of the certificate in the SDP and >>> ensuring >>> that the SDP has suitable integrity protection. When SIP is used to >>> transport the SDP, the integrity can be provided by the SIP Identity >>> mechanism. The rest of this section describes the details of this >>> approach. >>> >>> If self-signed certificates are used, the content of the subjectAltName >>> attribute inside the certificate MAY use the uniform resource >>> identifier >>> (URI) of the user. >> >> Can you make it clear here that you are talking about the AoR? >> >>> This is useful for debugging purposes only and is not >>> required to bind the certificate to one of the communication >>> endpoints. The >>> subjectAltName is not an important component of the certificate >>> verification. If the endpoint is also able to make anonymous >>> sessions, a >>> distinct, unique certificate MUST be used for this purpose. For an >>> client >>> that works with multiple users, each user SHOULD have its own >>> certificate. >>> The generation of public/private key pairs is relatively expensive. >>> Endpoints are not required to generate certificates for each session. >>> >>> A certificate fingerprint is the output of a one-way hash function >>> computed >>> over the distinguished encoding rules (DER) form of the certificate. >>> The >>> endpoint MUST use the certificate fingerprint attribute as specified >>> in [23] >>> and MUST include this in the SDP. >> >> A bit more text on how to include it in SDP would be good. Example >> would be great. >> >> Thanks, >> Hisham >> >>> The certificate presented during the TLS >>> handshake needs to match the fingerprint exchanged via the SDP and if >>> the >>> fingerprint does not match the hashed certificate then the endpoint >>> MUST >>> tear down the media session immediately. >>> >>> When using SIP, the integrity of the fingerprint can be ensured >>> through the >>> SIP Identity mechanism [22]. When a client wishes to use SIP to set >>> up a >>> secure MSRP session with another endpoint it sends an offer in a SIP >>> message >>> to the other endpoint. This offer includes, as part of the SDP >>> payload, the >>> fingerprint of the certificate that the endpoint wants to use. The SIP >>> message containing the offer is sent to the offerer's sip proxy which >>> will >>> add an identity header according to the procedures outlined in [22]. >>> When >>> the far endpoint receives the SIP message it can verify the identity >>> of the >>> sender using the identity header. Since the identity header is a >>> digital >>> signature across several SIP headers, in addition to the body or >>> bodies of >>> the SIP message, the receiver can also be certain that the message has >>> not >>> been tampered with after the digital signature was added to the SIP >>> message. >>> > > _______________________________________________ > Simple mailing list > Simple@ietf.org > https://www1.ietf.org/mailman/listinfo/simple > _______________________________________________ Simple mailing list Simple@ietf.org https://www1.ietf.org/mailman/listinfo/simple From simple-bounces@ietf.org Tue Dec 13 11:09:48 2005 Received: from localhost.cnri.reston.va.us ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1EmCiq-0004kz-JX; Tue, 13 Dec 2005 11:09:48 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1EmCip-0004kr-7m for simple@megatron.ietf.org; Tue, 13 Dec 2005 11:09:47 -0500 Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA14358 for ; Tue, 13 Dec 2005 11:08:49 -0500 (EST) Received: from rwcrmhc14.comcast.net ([216.148.227.89] helo=rwcrmhc12.comcast.net) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1EmCjq-00060T-8w for simple@ietf.org; Tue, 13 Dec 2005 11:10:51 -0500 Received: from s73602 (unknown[65.104.224.98]) by comcast.net (rwcrmhc14) with SMTP id <20051213160932014007ssp1e>; Tue, 13 Dec 2005 16:09:32 +0000 Message-ID: <04b701c5ffff$7a5d10b0$4e087c0a@china.huawei.com> From: "Spencer Dawkins" To: References: <439EC19E.2050504@nokia.com> Subject: Re: [Simple] Re: Addition to security sectiondraft-ietf-simple-message-sessions Date: Tue, 13 Dec 2005 10:08:37 -0600 MIME-Version: 1.0 Content-Type: text/plain; format=flowed; charset="iso-8859-1"; reply-type=response Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 6.00.2900.2180 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.2180 X-Spam-Score: 0.0 (/) X-Scan-Signature: 08e48e05374109708c00c6208b534009 Content-Transfer-Encoding: 7bit X-BeenThere: simple@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: SIP for Instant Messaging and Presence Leveraging Extensions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: simple-bounces@ietf.org Errors-To: simple-bounces@ietf.org > Last (but not least), seems like e2e TLS is only possible when there are > no relays, right? Then, doesn't that mean that NAT/FW traversal and e2e > security don't work together? Doesn't that really suck, if you have to > choose one or the other? This is a principle worthy of the IETF :-) Thanks, Aki, for sending it! Spencer _______________________________________________ Simple mailing list Simple@ietf.org https://www1.ietf.org/mailman/listinfo/simple From simple-bounces@ietf.org Tue Dec 13 12:04:48 2005 Received: from localhost.cnri.reston.va.us ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1EmDa4-0001Ha-5H; Tue, 13 Dec 2005 12:04:48 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1EmDa2-0001Fd-P0 for simple@megatron.ietf.org; Tue, 13 Dec 2005 12:04:46 -0500 Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA21206 for ; Tue, 13 Dec 2005 12:03:44 -0500 (EST) Received: from magus.nostrum.com ([69.5.195.2] helo=nostrum.com ident=root) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1EmDay-00080a-NS for simple@ietf.org; Tue, 13 Dec 2005 12:05:46 -0500 Received: from [172.17.2.252] (dsl001-129-069.dfw1.dsl.speakeasy.net [72.1.129.69]) (authenticated bits=0) by nostrum.com (8.12.11/8.12.11) with ESMTP id jBDH4JNf047477 (version=TLSv1/SSLv3 cipher=RC4-SHA bits=128 verify=NO); Tue, 13 Dec 2005 11:04:21 -0600 (CST) (envelope-from rjsparks@nostrum.com) In-Reply-To: <04b701c5ffff$7a5d10b0$4e087c0a@china.huawei.com> References: <439EC19E.2050504@nokia.com> <04b701c5ffff$7a5d10b0$4e087c0a@china.huawei.com> Mime-Version: 1.0 (Apple Message framework v746.2) X-Priority: 3 Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed Message-Id: <28ADC0ED-D4E4-45B4-8EE3-7140E58C0AF8@nostrum.com> Content-Transfer-Encoding: 7bit From: Robert Sparks Subject: Re: [Simple] Re: Addition to security sectiondraft-ietf-simple-message-sessions Date: Tue, 13 Dec 2005 11:04:18 -0600 To: Spencer Dawkins X-Mailer: Apple Mail (2.746.2) Received-SPF: pass (nostrum.com: 72.1.129.69 is authenticated by a trusted mechanism) X-Spam-Score: 0.0 (/) X-Scan-Signature: e1e48a527f609d1be2bc8d8a70eb76cb Content-Transfer-Encoding: 7bit Cc: simple@ietf.org X-BeenThere: simple@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: SIP for Instant Messaging and Presence Leveraging Extensions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: simple-bounces@ietf.org Errors-To: simple-bounces@ietf.org Of _course_ TLS only gives us e2e when there are not intermediaries terminating the TLS relationship. This additional section of text is describing how you can use TLS to your advantage in exactly that case. It is not defining a new e2e mechanism for the draft, nor is it claiming this is the only e2e mechanism available. From elsewhere in the document: Since MSRP carries arbitrary MIME content, it can trivially carry S/MIME protected messages as well. All MSRP implementations MUST support the multipart/signed MIME type even if they do not support S/MIME. Since SIP can carry a session key, S/MIME messages in the context of a session could also be protected using a key-wrapped shared secret [26] provided in the session setup. MSRP is a binary protocol and MIME bodies MUST be transferred with a transfer encoding of binary. If a message is both signed and encrypted, it SHOULD be signed first, then encrypted. If S/MIME is supported, SHA-1, RSA, and AES-128 MUST be supported. On Dec 13, 2005, at 10:08 AM, Spencer Dawkins wrote: >> Last (but not least), seems like e2e TLS is only possible when >> there are no relays, right? Then, doesn't that mean that NAT/FW >> traversal and e2e security don't work together? Doesn't that >> really suck, if you have to choose one or the other? > > This is a principle worthy of the IETF :-) Thanks, Aki, for sending > it! > > Spencer > > _______________________________________________ > Simple mailing list > Simple@ietf.org > https://www1.ietf.org/mailman/listinfo/simple _______________________________________________ Simple mailing list Simple@ietf.org https://www1.ietf.org/mailman/listinfo/simple From simple-bounces@ietf.org Wed Dec 14 02:13:36 2005 Received: from localhost.cnri.reston.va.us ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1EmQpU-0008MV-CB; Wed, 14 Dec 2005 02:13:36 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1EmIcO-0006lH-Ur for simple@megatron.ietf.org; Tue, 13 Dec 2005 17:27:35 -0500 Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA08434 for ; Tue, 13 Dec 2005 17:26:27 -0500 (EST) Received: from dsl001-129-069.dfw1.dsl.speakeasy.net ([72.1.129.69] helo=vicuna.estacado.net) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1EmIdL-0005On-O2 for simple@ietf.org; Tue, 13 Dec 2005 17:28:32 -0500 Received: from [172.17.2.252] ([172.17.2.252]) (authenticated bits=0) by vicuna.estacado.net (8.13.3/8.13.3) with ESMTP id jBDMR7BO084669 (version=TLSv1/SSLv3 cipher=RC4-SHA bits=128 verify=NO); Tue, 13 Dec 2005 16:27:08 -0600 (CST) (envelope-from rjsparks@estacado.net) In-Reply-To: <1134045864.3349.4.camel@w189.nomadiclab.com> References: <1134021749.3365.4.camel@n121.nomadiclab.com> <1134045864.3349.4.camel@w189.nomadiclab.com> Mime-Version: 1.0 (Apple Message framework v746.2) Content-Type: text/plain; charset=US-ASCII; format=flowed Message-Id: <0F6CC4AF-6F41-43F6-B7A8-AC690E4ED0AC@estacado.net> Content-Transfer-Encoding: 7bit From: Robert Sparks Date: Tue, 13 Dec 2005 16:27:06 -0600 To: Salvatore Loreto (JO/LMF) X-Mailer: Apple Mail (2.746.2) X-Spam-Score: 0.0 (/) X-Scan-Signature: 7d33c50f3756db14428398e2bdedd581 Content-Transfer-Encoding: 7bit X-Mailman-Approved-At: Wed, 14 Dec 2005 02:13:34 -0500 Cc: Robert Sparks , "simple@ietf.org list" Subject: [Simple] Re: simple-xcap in rfc editor queue X-BeenThere: simple@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: SIP for Instant Messaging and Presence Leveraging Extensions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: simple-bounces@ietf.org Errors-To: simple-bounces@ietf.org The plan is still for it to come off the queue. The gears are turning... If you haven't seen them already, the minutes capturing the plan are at http://www3.ietf.org/proceedings/05nov/minutes/simple.txt On Dec 8, 2005, at 6:44 AM, Salvatore Loreto (JO/LMF) wrote: > Hi all, > > I've just checked and the draft draft-ietf-simple-xcap is still in > RFC-Editor's Queue. > > When it'll be removed? > Or in other way what is the right process, or the process does the wg > want follow in this case? > > thank you > Sal > _______________________________________________ Simple mailing list Simple@ietf.org https://www1.ietf.org/mailman/listinfo/simple From simple-bounces@ietf.org Wed Dec 14 05:53:39 2005 Received: from localhost.cnri.reston.va.us ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1EmUGQ-0006gk-W6; Wed, 14 Dec 2005 05:53:39 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1EmUGO-0006gY-D5 for simple@megatron.ietf.org; Wed, 14 Dec 2005 05:53:36 -0500 Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id FAA04602 for ; Wed, 14 Dec 2005 05:52:38 -0500 (EST) From: Amitkumar.Goel@infineon.com Received: from smtp3.infineon.com ([203.126.106.229]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1EmUHW-0000Zs-Mm for simple@ietf.org; Wed, 14 Dec 2005 05:54:50 -0500 Received: from unknown (HELO sinse212.ap.infineon.com) ([172.17.65.148]) by smtp3.infineon.com with ESMTP; 14 Dec 2005 18:52:55 +0800 X-SBRS: None Received: from blrse201.ap.infineon.com ([172.20.20.12]) by sinse212.ap.infineon.com over TLS secured channel with Microsoft SMTPSVC(5.0.2195.6713); Wed, 14 Dec 2005 18:52:54 +0800 X-MimeOLE: Produced By Microsoft Exchange V6.0.6603.0 content-class: urn:content-classes:message MIME-Version: 1.0 Date: Wed, 14 Dec 2005 16:22:53 +0530 Message-ID: Thread-Topic: Multiple Media in MSRP SEND Request Thread-Index: AcYAnIhq01hcwOcoTbKdx3BOVynOHA== To: X-OriginalArrivalTime: 14 Dec 2005 10:52:54.0657 (UTC) FILETIME=[89640710:01C6009C] X-Spam-Score: 0.8 (/) X-Scan-Signature: 25620135586de10c627e3628c432b04a Subject: [Simple] Multiple Media in MSRP SEND Request X-BeenThere: simple@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: SIP for Instant Messaging and Presence Leveraging Extensions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============0817343261==" Sender: simple-bounces@ietf.org Errors-To: simple-bounces@ietf.org This is a multi-part message in MIME format. --===============0817343261== content-class: urn:content-classes:message Content-Type: multipart/alternative; boundary="----_=_NextPart_001_01C6009C.8871706F" This is a multi-part message in MIME format. ------_=_NextPart_001_01C6009C.8871706F Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable Hi All, =20 I am going through the draft-ietf-simple-message-sessions-11.txt and other related documents. I have one doubt. Is it possible to send multiple media in a same message? Suppose I am exchanging text messages to my friend by using MSRP session. At some point of time I also want to send some Audio along with the text message.=20 Is this scenario possible in MSRP session messaging? If yes, how will user create the SEND request? =20 Regards, Amit Kumar Goel Infineon Technology, 11th Floor, Discoverer Building, Whitefield,ITPL, Bangalore-560066 Ph: +91(080)41392721 Mobile:9448948977 =20 ------_=_NextPart_001_01C6009C.8871706F Content-Type: text/html; charset="us-ascii" Content-Transfer-Encoding: quoted-printable Message

Hi=20 All,

I am = going through=20 the draft-ietf-simple-message-sessions-11.txt=20 and other related documents. I have one doubt. Is it possible to send = multiple=20 media in a same message? Suppose I am exchanging text messages = to my friend by using MSRP session. At some = point of=20 time I also want to send some Audio along with the text message.=20

Is=20 this scenario possible in MSRP session messaging? If yes, = how=20 will user create the SEND request?

Regards,
Amit=20 Kumar Goel
Infineon Technology,
11th Floor, Discoverer=20 Building,
Whitefield,ITPL,
Bangalore-560066
Ph:=20 +91(080)41392721
Mobile:9448948977

------_=_NextPart_001_01C6009C.8871706F-- --===============0817343261== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ Simple mailing list Simple@ietf.org https://www1.ietf.org/mailman/listinfo/simple --===============0817343261==-- From simple-bounces@ietf.org Wed Dec 14 07:50:29 2005 Received: from localhost.cnri.reston.va.us ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1EmW5V-0003w4-GI; Wed, 14 Dec 2005 07:50:29 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1EmW5T-0003vX-Fa for simple@megatron.ietf.org; Wed, 14 Dec 2005 07:50:27 -0500 Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA18876 for ; Wed, 14 Dec 2005 07:49:28 -0500 (EST) Received: from zproxy.gmail.com ([64.233.162.192]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1EmW6e-0004tO-O9 for simple@ietf.org; Wed, 14 Dec 2005 07:51:42 -0500 Received: by zproxy.gmail.com with SMTP id v1so108660nzb for ; Wed, 14 Dec 2005 04:50:22 -0800 (PST) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:to:subject:in-reply-to:mime-version:content-type:references; b=rRTN46EF0R7m6PJAesrSv2QN+sDvTxf98/UafGPRk+SmLAzgBTmXFV6a03cvcVxbsuWFs0ZoHvS9kJPjPyKTtpPJYU8grmwB0cBN5HzaE2smV7Ug5CXF16wVYhORWx4a80VY/0ano35OZmbOY7PdipgWE0Rf+NrpywjoWwkr03o= Received: by 10.65.119.13 with SMTP id w13mr364411qbm; Wed, 14 Dec 2005 04:50:21 -0800 (PST) Received: by 10.65.236.15 with HTTP; Wed, 14 Dec 2005 04:50:21 -0800 (PST) Message-ID: <22e3bb730512140450i517e163bm8f7e2fa50748f98e@mail.gmail.com> Date: Wed, 14 Dec 2005 18:20:21 +0530 From: Vinod Joseph To: simple@ietf.org Subject: Re: [Simple] Multiple Media in MSRP SEND Request In-Reply-To: MIME-Version: 1.0 References: X-Spam-Score: 0.8 (/) X-Scan-Signature: 8de5f93cb2b4e3bee75302e9eacc33db X-BeenThere: simple@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: SIP for Instant Messaging and Presence Leveraging Extensions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============0498931789==" Sender: simple-bounces@ietf.org Errors-To: simple-bounces@ietf.org --===============0498931789== Content-Type: multipart/alternative; boundary="----=_Part_31758_18216149.1134564621848" ------=_Part_31758_18216149.1134564621848 Content-Type: text/plain; charset=ISO-8859-1 Content-Disposition: inline Content-Transfer-Encoding: quoted-printable SIP provides the opportunity for multiple media types in a single session o= r in related sessions to stay together, if that is what is desired. On 12/14/05, Amitkumar.Goel@infineon.com wrote: > > Hi All, > > I am going through the draft-ietf-simple-message-sessions-11.txt and othe= r > related documents. I have one doubt. Is it possible to send multiple medi= a > in a same message? Suppose I am exchanging text messages to my friend > by using MSRP session. At some point of time I also want to send some > Audio along with the text message. > Is this scenario possible in MSRP session messaging? If yes, how will use= r > create the SEND request? > > Regards, > Amit Kumar Goel > Infineon Technology, > 11th Floor, Discoverer Building, > Whitefield,ITPL, > Bangalore-560066 > Ph: +91(080)41392721 > Mobile:9448948977 > > > _______________________________________________ > Simple mailing list > Simple@ietf.org > https://www1.ietf.org/mailman/listinfo/simple > > > -- Vinod Cherian Joseph SISO ------=_Part_31758_18216149.1134564621848 Content-Type: text/html; charset=ISO-8859-1 Content-Disposition: inline Content-Transfer-Encoding: quoted-printable

SIP provides the opportunity for multiple media types in a si= ngle session or in related sessions to stay together, if that is what = is desired.

On 12/14/05, Amitkumar.Goel@infineon.com= <Amitkumar.Goel@= infineon.com > wrote:

Hi All,

I am going through the draft-ietf-simple-message-sessions-11.txt and other = related documents. I have one doubt. Is it possible to send multiple media = in a same message? Suppose I am exchanging text messages to = my friend by using MSRP session. At some point of time= I also want to send some Audio along with the text message.=20

= Is this scenario possible in MSRP session messaging? If yes,= how will user create the SEND request?

=

= Regards,
Amit Kumar Goel
Infineon Technology,
11th Floor, Discover= er Building,
Whitefield,ITPL,
Bangalore-560066
Ph: +91(080)4139272= 1
Mobile:9448948977

_______________= ________________________________
Simple mailing list
Simple@ietf.org
https://w= ww1.ietf.org/mailman/listinfo/simple

=

--
Vinod Cherian Joseph
SISO ------=_Part_31758_18216149.1134564621848-- --===============0498931789== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ Simple mailing list Simple@ietf.org https://www1.ietf.org/mailman/listinfo/simple --===============0498931789==-- From simple-bounces@ietf.org Wed Dec 14 09:08:34 2005 Received: from localhost.cnri.reston.va.us ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1EmXJ4-0006pA-3x; Wed, 14 Dec 2005 09:08:34 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1EmXJ2-0006oj-Pd for simple@megatron.ietf.org; Wed, 14 Dec 2005 09:08:33 -0500 Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA29021 for ; Wed, 14 Dec 2005 09:07:35 -0500 (EST) Received: from sj-iport-3-in.cisco.com ([171.71.176.72] helo=sj-iport-3.cisco.com) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1EmXKG-0008CA-2Q for simple@ietf.org; Wed, 14 Dec 2005 09:09:48 -0500 Received: from sj-core-5.cisco.com ([171.71.177.238]) by sj-iport-3.cisco.com with ESMTP; 14 Dec 2005 06:08:23 -0800 X-IronPort-AV: i="3.99,251,1131350400"; d="scan'208"; a="378132388:sNHT32262520" Received: from xbh-rtp-211.amer.cisco.com (xbh-rtp-211.cisco.com [64.102.31.102]) by sj-core-5.cisco.com (8.12.10/8.12.6) with ESMTP id jBEE8DQQ020538; Wed, 14 Dec 2005 06:08:21 -0800 (PST) Received: from xfe-rtp-202.amer.cisco.com ([64.102.31.21]) by xbh-rtp-211.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.211); Wed, 14 Dec 2005 09:08:17 -0500 Received: from [10.86.240.38] ([10.86.240.38]) by xfe-rtp-202.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.211); Wed, 14 Dec 2005 09:08:16 -0500 Message-ID: <43A02750.2000802@cisco.com> Date: Wed, 14 Dec 2005 09:08:16 -0500 From: Paul Kyzivat User-Agent: Mozilla Thunderbird 1.0.6 (Windows/20050716) X-Accept-Language: en-us, en MIME-Version: 1.0 To: Amitkumar.Goel@infineon.com Subject: Re: [Simple] Multiple Media in MSRP SEND Request References: In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-OriginalArrivalTime: 14 Dec 2005 14:08:16.0688 (UTC) FILETIME=[D4440300:01C600B7] X-Spam-Score: 0.0 (/) X-Scan-Signature: 39bd8f8cbb76cae18b7e23f7cf6b2b9f Content-Transfer-Encoding: 7bit Cc: simple@ietf.org X-BeenThere: simple@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: SIP for Instant Messaging and Presence Leveraging Extensions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: simple-bounces@ietf.org Errors-To: simple-bounces@ietf.org The only constraint over what you put in the messages is the set of content types that are negotiated in the offer/answer. If you negotiate the use of mutiple mime types that represent different media then you are free to use one type in one SEND and a different type in another SEND. And if you negotiate the use of multipart then you can include multiple types in the same SEND. Paul Amitkumar.Goel@infineon.com wrote: > Hi All, > > I am going through the draft-ietf-simple-message-sessions-11.txt and > other related documents. I have one doubt. Is it possible to send > multiple media in a same message? Suppose I am exchanging text messages > to my friend by using MSRP session. At some point of time I also want > to send some Audio along with the text message. > Is this scenario possible in MSRP session messaging? If yes, how will > user create the SEND request? > > Regards, > Amit Kumar Goel > Infineon Technology, > 11th Floor, Discoverer Building, > Whitefield,ITPL, > Bangalore-560066 > Ph: +91(080)41392721 > Mobile:9448948977 > > > > ------------------------------------------------------------------------ > > _______________________________________________ > Simple mailing list > Simple@ietf.org > https://www1.ietf.org/mailman/listinfo/simple _______________________________________________ Simple mailing list Simple@ietf.org https://www1.ietf.org/mailman/listinfo/simple From simple-bounces@ietf.org Wed Dec 14 19:37:36 2005 Received: from localhost.cnri.reston.va.us ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1Emh7o-0007hY-TW; Wed, 14 Dec 2005 19:37:36 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1Emh7j-0007gw-Ac for simple@megatron.ietf.org; Wed, 14 Dec 2005 19:37:35 -0500 Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA19666 for ; Wed, 14 Dec 2005 19:36:24 -0500 (EST) Received: from sj-iport-4.cisco.com ([171.68.10.86]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1Emh8q-0000Tv-13 for simple@ietf.org; Wed, 14 Dec 2005 19:38:44 -0500 Received: from sj-core-3.cisco.com ([171.68.223.137]) by sj-iport-4.cisco.com with ESMTP; 14 Dec 2005 16:37:09 -0800 Received: from vtg-um-e2k4.sj21ad.cisco.com (vtg-um-e2k4.cisco.com [171.70.93.57]) by sj-core-3.cisco.com (8.12.10/8.12.6) with ESMTP id jBF0b7Me023402; Wed, 14 Dec 2005 16:37:08 -0800 (PST) Received: from 128.107.139.242 ([128.107.139.242]) by vtg-um-e2k4.sj21ad.cisco.com ([171.70.93.57]) with Microsoft Exchange Server HTTP-DAV ; Thu, 15 Dec 2005 00:37:07 +0000 User-Agent: Microsoft-Entourage/11.2.1.051004 Date: Wed, 14 Dec 2005 16:37:15 -0800 Subject: Re: [Simple] Multiple Media in MSRP SEND Request From: Cullen Jennings To: Paul H Kyzivat , Message-ID: Thread-Topic: [Simple] Multiple Media in MSRP SEND Request Thread-Index: AcYBD7IN8MetvG0CEdqJKAARJEEJ/A== In-Reply-To: <43A02750.2000802@cisco.com> Mime-version: 1.0 Content-type: text/plain; charset="US-ASCII" Content-transfer-encoding: 7bit X-Spam-Score: 0.0 (/) X-Scan-Signature: 0ddefe323dd869ab027dbfff7eff0465 Content-Transfer-Encoding: 7bit Cc: "simple@ietf.org" X-BeenThere: simple@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: SIP for Instant Messaging and Presence Leveraging Extensions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: simple-bounces@ietf.org Errors-To: simple-bounces@ietf.org Yes, what Paul said. Imagine you wanted to sent a GIF image of yourself, a vcard with your contact information, and the message "Hello" all at the same time. You could send these with three SEND requests all at the same time. On 12/14/05 6:08 AM, "Paul Kyzivat" wrote: > The only constraint over what you put in the messages is the set of > content types that are negotiated in the offer/answer. If you negotiate > the use of mutiple mime types that represent different media then you > are free to use one type in one SEND and a different type in another > SEND. And if you negotiate the use of multipart then you can include > multiple types in the same SEND. > > Paul > > Amitkumar.Goel@infineon.com wrote: >> Hi All, >> >> I am going through the draft-ietf-simple-message-sessions-11.txt and >> other related documents. I have one doubt. Is it possible to send >> multiple media in a same message? Suppose I am exchanging text messages >> to my friend by using MSRP session. At some point of time I also want >> to send some Audio along with the text message. >> Is this scenario possible in MSRP session messaging? If yes, how will >> user create the SEND request? >> >> Regards, >> Amit Kumar Goel >> Infineon Technology, >> 11th Floor, Discoverer Building, >> Whitefield,ITPL, >> Bangalore-560066 >> Ph: +91(080)41392721 >> Mobile:9448948977 >> >> >> >> ------------------------------------------------------------------------ >> >> _______________________________________________ >> Simple mailing list >> Simple@ietf.org >> https://www1.ietf.org/mailman/listinfo/simple > > _______________________________________________ > Simple mailing list > Simple@ietf.org > https://www1.ietf.org/mailman/listinfo/simple _______________________________________________ Simple mailing list Simple@ietf.org https://www1.ietf.org/mailman/listinfo/simple From simple-bounces@ietf.org Wed Dec 14 19:41:41 2005 Received: from localhost.cnri.reston.va.us ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1EmhBl-0008E8-0l; Wed, 14 Dec 2005 19:41:41 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1EmhBj-0008Dp-Fg for simple@megatron.ietf.org; Wed, 14 Dec 2005 19:41:39 -0500 Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA19996 for ; Wed, 14 Dec 2005 19:40:40 -0500 (EST) Received: from sj-iport-1-in.cisco.com ([171.71.176.70] helo=sj-iport-1.cisco.com) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1EmhD1-0000c6-EI for simple@ietf.org; Wed, 14 Dec 2005 19:43:00 -0500 Received: from sj-core-5.cisco.com ([171.71.177.238]) by sj-iport-1.cisco.com with ESMTP; 14 Dec 2005 16:41:29 -0800 X-IronPort-AV: i="3.99,255,1131350400"; d="scan'208"; a="684752265:sNHT31731304" Received: from vtg-um-e2k4.sj21ad.cisco.com (vtg-um-e2k4.cisco.com [171.70.93.57]) by sj-core-5.cisco.com (8.12.10/8.12.6) with ESMTP id jBF0fQQK021163; Wed, 14 Dec 2005 16:41:27 -0800 (PST) Received: from 128.107.139.242 ([128.107.139.242]) by vtg-um-e2k4.sj21ad.cisco.com ([171.70.93.57]) with Microsoft Exchange Server HTTP-DAV ; Thu, 15 Dec 2005 00:41:26 +0000 User-Agent: Microsoft-Entourage/11.2.1.051004 Date: Wed, 14 Dec 2005 16:41:34 -0800 Subject: Re: [Simple] IMDN Issue #1: Security of IMDN From: Cullen Jennings To: Eric Burger Message-ID: Thread-Topic: [Simple] IMDN Issue #1: Security of IMDN Thread-Index: AcX5ygqNRz99IFFbS4ezLwACE5TCZgFfRlYmAAgUujAAajVobA== In-Reply-To: <330A23D8336C0346B5C1A5BB1966664701C7D74A@ATLANTIS.Brooktrout.com> Mime-version: 1.0 Content-type: text/plain; charset="US-ASCII" Content-transfer-encoding: 7bit X-Spam-Score: 0.0 (/) X-Scan-Signature: 50a516d93fd399dc60588708fd9a3002 Content-Transfer-Encoding: 7bit Cc: "simple@ietf.org" X-BeenThere: simple@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: SIP for Instant Messaging and Presence Leveraging Extensions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: simple-bounces@ietf.org Errors-To: simple-bounces@ietf.org On 12/12/05 3:50 PM, "Burger, Eric" wrote: > How about: > > 1. If UAS has a certificate, MUST sign IMDN. > that sounds good. > 2. If message was encrypted, MUST encrypt IMDN. Doesn't encrypting > cover signing? If not, to encrypt, need cert, so see rule 1. You can encrypt without signing. To encrypt a message from A to B, A needs to have B's cert but A does not have to have a cert. However, I think that I agree with your proposal here if message was encrypted, MUST encrypt IMDN and if you can't encrypt the IMDN then MUST NOT send it. > > -----Original Message----- > From: Cullen Jennings [mailto:fluffy@cisco.com] > Sent: Monday, December 12, 2005 1:09 PM > To: Burger, Eric; simple@ietf.org > Subject: Re: [Simple] IMDN Issue #1: Security of IMDN > > On 12/5/05 10:31 AM, "Burger, Eric" wrote: > >> Proposal is that if the body of the message was encrypted or signed, > the >> IMDN MUST be encrypted or signed, otherwise it MAY be plain text. >> >> Any dissent? > > If the IMDN was only signed, but the original message was encrypted, > would > the IMDN reveal anything that was not in the unencrypted portion of the > message? > > This proposal does seem a little weird - what happens if you can't sign > the > IMDN? > > Perhaps we might want something like the following 3 rules > > Always sign the IMDN if you have a cert. > > If the message was singed and encrypted, MUST encrypt repose. > > If the message was encrypted, MUST sign IMDN. > > _______________________________________________ Simple mailing list Simple@ietf.org https://www1.ietf.org/mailman/listinfo/simple From simple-bounces@ietf.org Wed Dec 14 22:45:53 2005 Received: from localhost.cnri.reston.va.us ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1Emk40-0003uW-5C; Wed, 14 Dec 2005 22:45:52 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1Emk3y-0003tW-B9 for simple@megatron.ietf.org; Wed, 14 Dec 2005 22:45:50 -0500 Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id WAA05678 for ; Wed, 14 Dec 2005 22:44:40 -0500 (EST) From: Amitkumar.Goel@infineon.com Received: from smtp3.infineon.com ([203.126.106.229]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1Emk54-0006PQ-FF for simple@ietf.org; Wed, 14 Dec 2005 22:47:00 -0500 Received: from unknown (HELO sinse212.ap.infineon.com) ([172.17.65.148]) by smtp3.infineon.com with ESMTP; 15 Dec 2005 11:45:17 +0800 X-SBRS: None Received: from blrse201.ap.infineon.com ([172.20.20.12]) by sinse212.ap.infineon.com over TLS secured channel with Microsoft SMTPSVC(5.0.2195.6713); Thu, 15 Dec 2005 11:45:12 +0800 X-MimeOLE: Produced By Microsoft Exchange V6.0.6603.0 content-class: urn:content-classes:message MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable Subject: RE: [Simple] Multiple Media in MSRP SEND Request Date: Thu, 15 Dec 2005 09:15:11 +0530 Message-ID: Thread-Topic: [Simple] Multiple Media in MSRP SEND Request Thread-Index: AcYBD7IN8MetvG0CEdqJKAARJEEJ/AAGYVWw To: , X-OriginalArrivalTime: 15 Dec 2005 03:45:12.0911 (UTC) FILETIME=[F43615F0:01C60129] X-Spam-Score: 0.3 (/) X-Scan-Signature: cd26b070c2577ac175cd3a6d878c6248 Content-Transfer-Encoding: quoted-printable Cc: simple@ietf.org X-BeenThere: simple@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: SIP for Instant Messaging and Presence Leveraging Extensions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: simple-bounces@ietf.org Errors-To: simple-bounces@ietf.org How other side know abt that all of the three send request belongs to the same message? Will use continuation flag (+) in the end line solve this problem? Regards, Amit Kumar Goel Infineon Technology, 11th Floor, Discoverer Building, Whitefield,ITPL, Bangalore-560066 Ph: +91(080)41392721 Mobile:9448948977 -----Original Message----- From: Cullen Jennings [mailto:fluffy@cisco.com]=20 Sent: Thursday, December 15, 2005 6:07 AM To: Paul H Kyzivat; Goel Amitkumar (IFIN CSW WS) Cc: simple@ietf.org Subject: Re: [Simple] Multiple Media in MSRP SEND Request Yes, what Paul said. Imagine you wanted to sent a GIF image of yourself, a vcard with your contact information, and the message "Hello" all at the same time. You could send these with three SEND requests all at the same time. On 12/14/05 6:08 AM, "Paul Kyzivat" wrote: > The only constraint over what you put in the messages is the set of=20 > content types that are negotiated in the offer/answer. If you=20 > negotiate the use of mutiple mime types that represent different media > then you are free to use one type in one SEND and a different type in=20 > another SEND. And if you negotiate the use of multipart then you can=20 > include multiple types in the same SEND. >=20 > Paul >=20 > Amitkumar.Goel@infineon.com wrote: >> Hi All, >> =20 >> I am going through the draft-ietf-simple-message-sessions-11.txt and=20 >> other related documents. I have one doubt. Is it possible to send=20 >> multiple media in a same message? Suppose I am exchanging text=20 >> messages to my friend by using MSRP session. At some point of time I >> also want to send some Audio along with the text message. Is this=20 >> scenario possible in MSRP session messaging? If yes, how will user=20 >> create the SEND request? >> =20 >> Regards, >> Amit Kumar Goel >> Infineon Technology, >> 11th Floor, Discoverer Building, >> Whitefield,ITPL, >> Bangalore-560066 >> Ph: +91(080)41392721 >> Mobile:9448948977 >> =20 >>=20 >>=20 >> --------------------------------------------------------------------- >> --- >>=20 >> _______________________________________________ >> Simple mailing list >> Simple@ietf.org https://www1.ietf.org/mailman/listinfo/simple >=20 > _______________________________________________ > Simple mailing list > Simple@ietf.org > https://www1.ietf.org/mailman/listinfo/simple _______________________________________________ Simple mailing list Simple@ietf.org https://www1.ietf.org/mailman/listinfo/simple From simple-bounces@ietf.org Thu Dec 15 00:04:10 2005 Received: from localhost.cnri.reston.va.us ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1EmlHm-0007y1-US; Thu, 15 Dec 2005 00:04:10 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1EmlHh-0007wu-1g for simple@megatron.ietf.org; Thu, 15 Dec 2005 00:04:09 -0500 Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id AAA13123 for ; Thu, 15 Dec 2005 00:02:58 -0500 (EST) Received: from sj-iport-3-in.cisco.com ([171.71.176.72] helo=sj-iport-3.cisco.com) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1EmlIs-0000hI-Mj for simple@ietf.org; Thu, 15 Dec 2005 00:05:20 -0500 Received: from sj-core-1.cisco.com ([171.71.177.237]) by sj-iport-3.cisco.com with ESMTP; 14 Dec 2005 21:03:46 -0800 X-IronPort-AV: i="3.99,256,1131350400"; d="scan'208"; a="378499471:sNHT34207726" Received: from xbh-rtp-211.amer.cisco.com (xbh-rtp-211.cisco.com [64.102.31.102]) by sj-core-1.cisco.com (8.12.10/8.12.6) with ESMTP id jBF53e72010395; Wed, 14 Dec 2005 21:03:43 -0800 (PST) Received: from xfe-rtp-202.amer.cisco.com ([64.102.31.21]) by xbh-rtp-211.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.211); Thu, 15 Dec 2005 00:03:40 -0500 Received: from [10.86.240.38] ([10.86.240.38]) by xfe-rtp-202.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.211); Thu, 15 Dec 2005 00:03:39 -0500 Message-ID: <43A0F92B.9020807@cisco.com> Date: Thu, 15 Dec 2005 00:03:39 -0500 From: Paul Kyzivat User-Agent: Mozilla Thunderbird 1.0.6 (Windows/20050716) X-Accept-Language: en-us, en MIME-Version: 1.0 To: Amitkumar.Goel@infineon.com Subject: Re: [Simple] Multiple Media in MSRP SEND Request References: In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-OriginalArrivalTime: 15 Dec 2005 05:03:39.0764 (UTC) FILETIME=[E9B6DB40:01C60134] X-Spam-Score: 0.0 (/) X-Scan-Signature: 386e0819b1192672467565a524848168 Content-Transfer-Encoding: 7bit Cc: fluffy@cisco.com, simple@ietf.org X-BeenThere: simple@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: SIP for Instant Messaging and Presence Leveraging Extensions List-Unsubscribe: , List-Archive: List-Post: