From simple-admin@mailman.dynamicsoft.com Tue Dec 3 10:22:35 2002 Received: from mail1.dynamicsoft.com (mail1.dynamicsoft.com [63.113.40.10]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA25773 for ; Tue, 3 Dec 2002 10:22:34 -0500 (EST) Received: from mailman.dynamicsoft.com ([192.168.4.50]) by mail1.dynamicsoft.com (8.12.0.Beta7/8.12.0.Beta7) with ESMTP id gB3FK8Q4005310; Tue, 3 Dec 2002 10:20:08 -0500 (EST) Received: from mailman.dynamicsoft.com (localhost [127.0.0.1]) by mailman.dynamicsoft.com (8.9.3+Sun/8.9.3) with ESMTP id KAA05443; Tue, 3 Dec 2002 10:21:08 -0500 (EST) Received: from dyn-tx-arch-crash.dfw.dynamicsoft.com (dyn-tx-arch-crash.dfw.dynamicsoft.com [63.110.3.64]) by mailman.dynamicsoft.com (8.9.3+Sun/8.9.3) with ESMTP id KAA05428 for ; Tue, 3 Dec 2002 10:20:29 -0500 (EST) Received: from RjS.localdomain (localhost.localdomain [127.0.0.1]) by dyn-tx-arch-crash.dfw.dynamicsoft.com (8.11.6/8.11.6) with ESMTP id gB3FKVI02442 for ; Tue, 3 Dec 2002 09:20:31 -0600 From: Robert Sparks To: simple@mailman.dynamicsoft.com Content-Type: text/plain Content-Transfer-Encoding: 7bit X-Mailer: Ximian Evolution 1.0.8 (1.0.8-10) Message-Id: <1038928789.944.30.camel@RjS.localdomain> Mime-Version: 1.0 Subject: [Simple] SIPIT 12 registration is open Sender: simple-admin@mailman.dynamicsoft.com Errors-To: simple-admin@mailman.dynamicsoft.com X-BeenThere: simple@mailman.dynamicsoft.com X-Mailman-Version: 2.0 Precedence: bulk List-Help: List-Post: List-Subscribe: , List-Id: SIP for Presence List-Unsubscribe: , List-Archive: Date: 03 Dec 2002 09:19:49 -0600 Content-Transfer-Encoding: 7bit The 12th SIPit will be hosted by Hotsip in Stockholm February 24-28, 2003. Please see http://www.hotsip.com/sipit12/ for details and registration. There were several SIMPLE implementations at the last SIPIT. I expect more at this one (drop me a note if you're planning to attend). We will have a multiparty session testing SIMPLE interoperability at this event. Thanks, RjS _______________________________________________ simple mailing list simple@mailman.dynamicsoft.com http://mailman.dynamicsoft.com/mailman/listinfo/simple From simple-admin@mailman.dynamicsoft.com Tue Dec 3 15:31:20 2002 Received: from mail1.dynamicsoft.com (mail1.dynamicsoft.com [63.113.40.10]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA16426 for ; Tue, 3 Dec 2002 15:31:19 -0500 (EST) Received: from mailman.dynamicsoft.com ([192.168.4.50]) by mail1.dynamicsoft.com (8.12.0.Beta7/8.12.0.Beta7) with ESMTP id gB3KM4Q4006734; Tue, 3 Dec 2002 15:22:04 -0500 (EST) Received: from mailman.dynamicsoft.com (localhost [127.0.0.1]) by mailman.dynamicsoft.com (8.9.3+Sun/8.9.3) with ESMTP id PAA06451; Tue, 3 Dec 2002 15:23:05 -0500 (EST) Received: from mail3.dynamicsoft.com (mail3.dynamicsoft.com [63.113.44.69]) by mailman.dynamicsoft.com (8.9.3+Sun/8.9.3) with ESMTP id PAA06440 for ; Tue, 3 Dec 2002 15:22:31 -0500 (EST) Received: from dynamicsoft.com ([63.113.46.55]) by mail3.dynamicsoft.com (8.12.1/8.12.1) with ESMTP id gB3KMZYH011415 for ; Tue, 3 Dec 2002 15:22:35 -0500 (EST) Message-ID: <3DED1284.9020207@dynamicsoft.com> From: Jonathan Rosenberg Organization: dynamicsoft User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.1) Gecko/20020826 X-Accept-Language: en-us, en MIME-Version: 1.0 To: simple@mailman.dynamicsoft.com Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Subject: [Simple] Updated presence specs Sender: simple-admin@mailman.dynamicsoft.com Errors-To: simple-admin@mailman.dynamicsoft.com X-BeenThere: simple@mailman.dynamicsoft.com X-Mailman-Version: 2.0 Precedence: bulk List-Help: List-Post: List-Subscribe: , List-Id: SIP for Presence List-Unsubscribe: , List-Archive: Date: Tue, 03 Dec 2002 15:22:28 -0500 Content-Transfer-Encoding: 7bit Folks, I've just submitted an update to all three core presence specs (presence, watcherinfo package, watcherinfo format) based on comments received during last call, including those from our AD. Until they appear in the archives, you can pick them up at: http://www.jdrosen.net/papers/draft-ietf-simple-presence-08.txt http://www.jdrosen.net/papers/draft-ietf-simple-winfo-package-03.txt http://www.jdrosen.net/papers/draft-ietf-simple-winfo-format-03.txt THe changes are mostly minor. Below you will find a summary. PRESENCE -------- * reduced the author list to one, as I have been the primary author and editor for some time. This was at the request of Patrik, and is consistent with RFC-editor policy on author lists. The remainder of the author list was moved to a contributor section. * Section 4, overview of operation, reported that a SUBSCRIBE with Expires: 0, used for fetch, was identical to processing of a SUBSCRIBE with a non-zero Expires, in that both result in an immediate NOTIFY. This isn't true. An immediate NOTIFY is only sent, in all cases, when the SUBSCRIBE is either pending or authorized. Clarified that. * Reworked the section on replay prevention. Added a few paragraphs describing why replay was bad. Remvoed the text which talked about including Call-ID, CSeq and Date headers in the signature; that requires the use of message/sip signed bodies and was not the intent. Rather, the signature is just over the PIDF document. PIDF provides its own timestamp for replay prevention; the spec now mandates its usage. I also added some verbiage on how and when http digest can be used to provide replay protection. * The section on DoS attack prevention described a check that the UA could make. If the From field domain and the Contact domain didn't match, inform the user. However, this is really useless, since frequently the Contact header field will contain an IP address. This attack is better prevented by authentication and authorization, and if it does happen, timeouts and NOTIFY rejections remove a subscription anyway. Thus, it is adequately handled without this text. The text was therefore removed. * Split the DoS protection section into two - one section addressing attacks against third parties (the text that was there before), and a new subsection on attacks against the server itself. In that section, added a brief discussion on standard sip techniques for dealing with such attacks. * Made section heading capitalizations consistent. * More formal terminology alignment with rfc 2778 in the introduction. * Updated references * Change CPIM references to CPP, based on the document split in IMPP. * Updated the usage of presence URIs to reflect current consensus on this issue in IMPP. * Removed the text in 6.6 about generating a 403 if the PA doesn't want to accept forwarded subscribe requests. This text pre-dated the inclusion of equivalent text in RFC 3261. Since the text is now in RFC 3261, there is no need to repeat it here. * Removed text in section 6.6.1 about obtaining subscriber identity in networks of transitive trust. This paragraph predates the now extensive work on network asserted identity for sip. The paragraph merely states that identity establishment through transitive trust is one approach in inter-domain networks, and cites the relevant I-Ds on the subject as non-normative approaches. This includes the P-NAI header and the more recent identity work using authenticated identity bodies. * aligned with latest caller preferences spec. In particular, it is now a SHOULD for a PUA that can support PA function to indicate support for both SUBSCRIBE method and the presence event package. * fixed up the presentation of the section on migration and state agents. In particular, the text is more explicit in meeting the requirements outlined in RFC 3265 for this section, in that it now talks about authentication and authorization. The migration text was streamlined a bit, removing some of the redundant definitions. * There was never a normative strength associated with implementing the watcherinfo package in presence servers. Since authorization in state agents must be considered by any event package, support for that package was made a SHOULD. * general improvements in wording, attempting to be more brief and switch from passive to active tense (I have a habit of writing in passive tense). * Updated the text on creating presence documents from registrations - terminology fixes and clarifications. Also state that the means by which registrations are turned into presence documents is a matter of policy. WINFO PACKAGE -------------- * changed title to reflect SIP guidelines * fixed Via header in example NOTIFY request in Section 3.1 * updated references WINFO FORMAT ------------ * updated references * indicate that version numbers dont wrap. Thanks, Jonathan R. -- Jonathan D. Rosenberg, Ph.D. 72 Eagle Rock Ave. Chief Scientist First Floor dynamicsoft East Hanover, NJ 07936 jdrosen@dynamicsoft.com FAX: (973) 952-5050 http://www.jdrosen.net PHONE: (973) 952-5000 http://www.dynamicsoft.com _______________________________________________ simple mailing list simple@mailman.dynamicsoft.com http://mailman.dynamicsoft.com/mailman/listinfo/simple From simple-admin@mailman.dynamicsoft.com Thu Dec 5 09:24:09 2002 Received: from mail1.dynamicsoft.com (mail1.dynamicsoft.com [63.113.40.10]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA12765 for ; Thu, 5 Dec 2002 09:24:09 -0500 (EST) Received: from mailman.dynamicsoft.com ([192.168.4.50]) by mail1.dynamicsoft.com (8.12.0.Beta7/8.12.0.Beta7) with ESMTP id gB5EP6Q4013300; Thu, 5 Dec 2002 09:25:06 -0500 (EST) Received: from mailman.dynamicsoft.com (localhost [127.0.0.1]) by mailman.dynamicsoft.com (8.9.3+Sun/8.9.3) with ESMTP id JAA13871; Thu, 5 Dec 2002 09:26:08 -0500 (EST) Received: from ietf.org (odin.ietf.org [132.151.1.176]) by mailman.dynamicsoft.com (8.9.3+Sun/8.9.3) with ESMTP id JAA13860 for ; Thu, 5 Dec 2002 09:25:02 -0500 (EST) Received: from CNRI.Reston.VA.US (localhost [127.0.0.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA12641; Thu, 5 Dec 2002 09:22:11 -0500 (EST) Message-Id: <200212051422.JAA12641@ietf.org> Mime-Version: 1.0 Content-Type: Multipart/Mixed; Boundary="NextPart" To: IETF-Announce: ; Cc: simple@mailman.dynamicsoft.com From: Internet-Drafts@ietf.org Reply-to: Internet-Drafts@ietf.org Subject: [Simple] I-D ACTION:draft-ietf-simple-presence-08.txt Sender: simple-admin@mailman.dynamicsoft.com Errors-To: simple-admin@mailman.dynamicsoft.com X-BeenThere: simple@mailman.dynamicsoft.com X-Mailman-Version: 2.0 Precedence: bulk List-Help: List-Post: List-Subscribe: , List-Id: SIP for Presence List-Unsubscribe: , List-Archive: Date: Thu, 05 Dec 2002 09:22:11 -0500 --NextPart 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 : A Presence Event Package for the Session Initiation Protocol (SIP) Author(s) : J. Rosenberg Filename : draft-ietf-simple-presence-08.txt Pages : 26 Date : 2002-12-4 This document describes the usage of the Session Initiation Protocol (SIP) for subscriptions and notifications of presence. Presence is defined as the willingness and ability of a user to communicate with other users on the network. Historically, presence has been limited to 'on-line' and 'off-line' indicators; the notion of presence here is broader. Subscriptions and notifications of presence are supported by defining an event package within the general SIP event notification framework. This protocol is also compliant with the Common Presence Profile (CPP) framework. A URL for this Internet-Draft is: http://www.ietf.org/internet-drafts/draft-ietf-simple-presence-08.txt To remove yourself from the IETF Announcement list, send a message to ietf-announce-request with the word unsubscribe in the body of the message. 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-presence-08.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-presence-08.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. --NextPart Content-Type: Multipart/Alternative; Boundary="OtherAccess" --OtherAccess Content-Type: Message/External-body; access-type="mail-server"; server="mailserv@ietf.org" Content-Type: text/plain Content-ID: <2002-12-4093321.I-D@ietf.org> ENCODING mime FILE /internet-drafts/draft-ietf-simple-presence-08.txt --OtherAccess Content-Type: Message/External-body; name="draft-ietf-simple-presence-08.txt"; site="ftp.ietf.org"; access-type="anon-ftp"; directory="internet-drafts" Content-Type: text/plain Content-ID: <2002-12-4093321.I-D@ietf.org> --OtherAccess-- --NextPart-- _______________________________________________ simple mailing list simple@mailman.dynamicsoft.com http://mailman.dynamicsoft.com/mailman/listinfo/simple From simple-admin@mailman.dynamicsoft.com Thu Dec 5 09:27:52 2002 Received: from mail1.dynamicsoft.com (mail1.dynamicsoft.com [63.113.40.10]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA12959 for ; Thu, 5 Dec 2002 09:27:52 -0500 (EST) Received: from mailman.dynamicsoft.com ([192.168.4.50]) by mail1.dynamicsoft.com (8.12.0.Beta7/8.12.0.Beta7) with ESMTP id gB5ESrQ4013408; Thu, 5 Dec 2002 09:28:53 -0500 (EST) Received: from mailman.dynamicsoft.com (localhost [127.0.0.1]) by mailman.dynamicsoft.com (8.9.3+Sun/8.9.3) with ESMTP id JAA13929; Thu, 5 Dec 2002 09:30:03 -0500 (EST) Received: from ietf.org (odin.ietf.org [132.151.1.176]) by mailman.dynamicsoft.com (8.9.3+Sun/8.9.3) with ESMTP id JAA13885 for ; Thu, 5 Dec 2002 09:28:43 -0500 (EST) Received: from CNRI.Reston.VA.US (localhost [127.0.0.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA12847; Thu, 5 Dec 2002 09:25:52 -0500 (EST) Message-Id: <200212051425.JAA12847@ietf.org> Mime-Version: 1.0 Content-Type: Multipart/Mixed; Boundary="NextPart" To: IETF-Announce: ; Cc: simple@mailman.dynamicsoft.com From: Internet-Drafts@ietf.org Reply-to: Internet-Drafts@ietf.org Subject: [Simple] I-D ACTION:draft-ietf-simple-winfo-package-03.txt Sender: simple-admin@mailman.dynamicsoft.com Errors-To: simple-admin@mailman.dynamicsoft.com X-BeenThere: simple@mailman.dynamicsoft.com X-Mailman-Version: 2.0 Precedence: bulk List-Help: List-Post: List-Subscribe: , List-Id: SIP for Presence List-Unsubscribe: , List-Archive: Date: Thu, 05 Dec 2002 09:25:52 -0500 --NextPart 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 : A Watcher Information Event Template-Package for the Session Initiation Protocol (SIP) Author(s) : J. Rosenberg Filename : draft-ietf-simple-winfo-package-03.txt Pages : 19 Date : 2002-12-4 This document defines the watcher information template-package for the SIP event framework. Watcher information refers to the set of users subscribed to a particular resource within a particular event package. Watcher information changes dynamically as users subscribe, unsubscribe, are approved, or are rejected. A user can subscribe to this information, and therefore learn about changes to it. This event package is a template-package because it can be applied to any event package, including itself. A URL for this Internet-Draft is: http://www.ietf.org/internet-drafts/draft-ietf-simple-winfo-package-03.txt To remove yourself from the IETF Announcement list, send a message to ietf-announce-request with the word unsubscribe in the body of the message. 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-winfo-package-03.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-winfo-package-03.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. --NextPart Content-Type: Multipart/Alternative; Boundary="OtherAccess" --OtherAccess Content-Type: Message/External-body; access-type="mail-server"; server="mailserv@ietf.org" Content-Type: text/plain Content-ID: <2002-12-4093332.I-D@ietf.org> ENCODING mime FILE /internet-drafts/draft-ietf-simple-winfo-package-03.txt --OtherAccess Content-Type: Message/External-body; name="draft-ietf-simple-winfo-package-03.txt"; site="ftp.ietf.org"; access-type="anon-ftp"; directory="internet-drafts" Content-Type: text/plain Content-ID: <2002-12-4093332.I-D@ietf.org> --OtherAccess-- --NextPart-- _______________________________________________ simple mailing list simple@mailman.dynamicsoft.com http://mailman.dynamicsoft.com/mailman/listinfo/simple From simple-admin@mailman.dynamicsoft.com Thu Dec 5 09:28:03 2002 Received: from mail1.dynamicsoft.com (mail1.dynamicsoft.com [63.113.40.10]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA12984 for ; Thu, 5 Dec 2002 09:28:02 -0500 (EST) Received: from mailman.dynamicsoft.com ([192.168.4.50]) by mail1.dynamicsoft.com (8.12.0.Beta7/8.12.0.Beta7) with ESMTP id gB5ET6Q4013437; Thu, 5 Dec 2002 09:29:06 -0500 (EST) Received: from mailman.dynamicsoft.com (localhost [127.0.0.1]) by mailman.dynamicsoft.com (8.9.3+Sun/8.9.3) with ESMTP id JAA13945; Thu, 5 Dec 2002 09:30:16 -0500 (EST) Received: from ietf.org (odin.ietf.org [132.151.1.176]) by mailman.dynamicsoft.com (8.9.3+Sun/8.9.3) with ESMTP id JAA13890 for ; Thu, 5 Dec 2002 09:28:49 -0500 (EST) Received: from CNRI.Reston.VA.US (localhost [127.0.0.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA12864; Thu, 5 Dec 2002 09:25:58 -0500 (EST) Message-Id: <200212051425.JAA12864@ietf.org> Mime-Version: 1.0 Content-Type: Multipart/Mixed; Boundary="NextPart" To: IETF-Announce: ; Cc: simple@mailman.dynamicsoft.com From: Internet-Drafts@ietf.org Reply-to: Internet-Drafts@ietf.org Subject: [Simple] I-D ACTION:draft-ietf-simple-winfo-format-03.txt Sender: simple-admin@mailman.dynamicsoft.com Errors-To: simple-admin@mailman.dynamicsoft.com X-BeenThere: simple@mailman.dynamicsoft.com X-Mailman-Version: 2.0 Precedence: bulk List-Help: List-Post: List-Subscribe: , List-Id: SIP for Presence List-Unsubscribe: , List-Archive: Date: Thu, 05 Dec 2002 09:25:58 -0500 --NextPart 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) Based Format for Watcher Information Author(s) : J. Rosenberg Filename : draft-ietf-simple-winfo-format-03.txt Pages : 14 Date : 2002-12-4 Watchers are defined as entities that request (i.e., subscribe to) information about a resource. There is fairly complex state associated with these subscriptions. The union of the state for all subscriptions to a particular resource is called the watcher information for that resource. This state is dynamic, changing as subscribers come and go. As a result, it is possible, and indeed useful, to subscribe to the watcher information for a particular resource. In order to enable this, a format is needed to describe the state of watchers on a resource. This specification describes an XML document format for such state. A URL for this Internet-Draft is: http://www.ietf.org/internet-drafts/draft-ietf-simple-winfo-format-03.txt To remove yourself from the IETF Announcement list, send a message to ietf-announce-request with the word unsubscribe in the body of the message. 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-winfo-format-03.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-winfo-format-03.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. --NextPart Content-Type: Multipart/Alternative; Boundary="OtherAccess" --OtherAccess Content-Type: Message/External-body; access-type="mail-server"; server="mailserv@ietf.org" Content-Type: text/plain Content-ID: <2002-12-4093341.I-D@ietf.org> ENCODING mime FILE /internet-drafts/draft-ietf-simple-winfo-format-03.txt --OtherAccess Content-Type: Message/External-body; name="draft-ietf-simple-winfo-format-03.txt"; site="ftp.ietf.org"; access-type="anon-ftp"; directory="internet-drafts" Content-Type: text/plain Content-ID: <2002-12-4093341.I-D@ietf.org> --OtherAccess-- --NextPart-- _______________________________________________ simple mailing list simple@mailman.dynamicsoft.com http://mailman.dynamicsoft.com/mailman/listinfo/simple From simple-admin@mailman.dynamicsoft.com Fri Dec 6 02:56:11 2002 Received: from mail1.dynamicsoft.com (mail1.dynamicsoft.com [63.113.40.10]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id CAA28134 for ; Fri, 6 Dec 2002 02:56:11 -0500 (EST) Received: from mailman.dynamicsoft.com ([192.168.4.50]) by mail1.dynamicsoft.com (8.12.0.Beta7/8.12.0.Beta7) with ESMTP id gB67v4Q4016954; Fri, 6 Dec 2002 02:57:04 -0500 (EST) Received: from mailman.dynamicsoft.com (localhost [127.0.0.1]) by mailman.dynamicsoft.com (8.9.3+Sun/8.9.3) with ESMTP id CAA17038; Fri, 6 Dec 2002 02:58:03 -0500 (EST) Received: from mail3.dynamicsoft.com (mail3.dynamicsoft.com [63.113.44.69]) by mailman.dynamicsoft.com (8.9.3+Sun/8.9.3) with ESMTP id CAA17027 for ; Fri, 6 Dec 2002 02:57:23 -0500 (EST) Received: from dynamicsoft.com ([63.113.46.83]) by mail3.dynamicsoft.com (8.12.1/8.12.1) with ESMTP id gB67vQYH012960 for ; Fri, 6 Dec 2002 02:57:26 -0500 (EST) Message-ID: <3DF05863.8000103@dynamicsoft.com> From: Jonathan Rosenberg Organization: dynamicsoft User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.1) Gecko/20020826 X-Accept-Language: en-us, en MIME-Version: 1.0 To: simple@mailman.dynamicsoft.com Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Subject: [Simple] minor updates to presence spec and watcherinfo spec Sender: simple-admin@mailman.dynamicsoft.com Errors-To: simple-admin@mailman.dynamicsoft.com X-BeenThere: simple@mailman.dynamicsoft.com X-Mailman-Version: 2.0 Precedence: bulk List-Help: List-Post: List-Subscribe: , List-Id: SIP for Presence List-Unsubscribe: , List-Archive: Date: Fri, 06 Dec 2002 02:57:23 -0500 Content-Transfer-Encoding: 7bit Folks, I've just submitted another update to the presence spec and the watcherinfo changes. The updates are minor and address further iesg comments. Until they appear in the archives, you can grab them from: http://www.jdrosen.net/papers/draft-ietf-simple-winfo-package-04.txt http://www.jdrosen.net/papers/draft-ietf-simple-presence-09.txt The changes are summarized below. PRESENCE -------- * in the pres URI discussion, it says that SIP URI is preferred when its known. Fixed to say SIP or SIPS URI, instead of just SIP URI. * removed references to p-header network asserted ID drafts as a means to establish identity. Text now reads: In inter-domain scenarios, establishing an authenticated identity of the subscriber is harder. It is anticipated that authentication will often be established through transitive trust. SIP mechanisms for network asserted identity can be applied to establish the identity of the subscriber \citenonnorm{draft-ietf-sip-identity}. * removed text which said that you can send notifications faster than once every 5 seconds if an extension explicitly says its OK. * explicit mention of rfc2779 as an influence on security considerations. * mention the possibility of e2e encryption using smime shared secrets (rfc3211). * changed examples to tcp WINFO-PACKAGE -------------- * Added JDR contact information to template package registration in IANA considerations section. -Jonathan R. -- Jonathan D. Rosenberg, Ph.D. 72 Eagle Rock Ave. Chief Scientist First Floor dynamicsoft East Hanover, NJ 07936 jdrosen@dynamicsoft.com FAX: (973) 952-5050 http://www.jdrosen.net PHONE: (973) 952-5000 http://www.dynamicsoft.com _______________________________________________ simple mailing list simple@mailman.dynamicsoft.com http://mailman.dynamicsoft.com/mailman/listinfo/simple From simple-admin@mailman.dynamicsoft.com Fri Dec 6 05:31:54 2002 Received: from mail1.dynamicsoft.com (mail1.dynamicsoft.com [63.113.40.10]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id FAA01191 for ; Fri, 6 Dec 2002 05:31:53 -0500 (EST) Received: from mailman.dynamicsoft.com ([192.168.4.50]) by mail1.dynamicsoft.com (8.12.0.Beta7/8.12.0.Beta7) with ESMTP id gB6AWvQ4017276; Fri, 6 Dec 2002 05:32:57 -0500 (EST) Received: from mailman.dynamicsoft.com (localhost [127.0.0.1]) by mailman.dynamicsoft.com (8.9.3+Sun/8.9.3) with ESMTP id FAA17513; Fri, 6 Dec 2002 05:34:03 -0500 (EST) Received: from himalaya.scicmp.com ([203.200.79.36]) by mailman.dynamicsoft.com (8.9.3+Sun/8.9.3) with SMTP id FAA17486 for ; Fri, 6 Dec 2002 05:26:07 -0500 (EST) Received: from mx1.scicmp.com ([10.130.0.5]) by himalaya.scicmp.com (NAVGW 2.5.2.12) with SMTP id M2002120615562530354 for ; Fri, 06 Dec 2002 15:56:25 +0530 Received: from scicmp.com (kanchenjunga [10.140.13.178]) by mx1.scicmp.com (8.9.3/8.8.7) with ESMTP id QAA31898 for ; Fri, 6 Dec 2002 16:03:21 +0530 Message-ID: <3DF07BF8.3AFF5BBE@scicmp.com> From: Sudipta Ghosh Organization: Scicom Infotech Pvt. Ltd. (Scicom) X-Mailer: Mozilla 4.79 [en] (Windows NT 5.0; U) X-Accept-Language: en,pdf MIME-Version: 1.0 To: simple Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Subject: [Simple] Event Sender: simple-admin@mailman.dynamicsoft.com Errors-To: simple-admin@mailman.dynamicsoft.com X-BeenThere: simple@mailman.dynamicsoft.com X-Mailman-Version: 2.0 Precedence: bulk List-Help: List-Post: List-Subscribe: , List-Id: SIP for Presence List-Unsubscribe: , List-Archive: Date: Fri, 06 Dec 2002 15:59:12 +0530 Content-Transfer-Encoding: 7bit Hi, When IM Client is sending a SUBSCRIPTION request( to a offline user ) for presence notification to proxy,proxy sends response with 200 OK but adds a event header. Whats the meaning of it. In REGISTER request there is also a Event header. I am sending the packets.(got from MSN Messenger communication service) SUBSCRIBE sip:sudipta@10.140.13.149 SIP/2.0 Via: SIP/2.0/TCP 10.140.13.178:9172 From: "i" ;tag=5a9e885b-5af7-45b4-ad41-33eb48ae6a99 To: Call-ID: 382d3998-db28-409d-b692-fedf56a685fe@10.140.13.178 CSeq: 1 SUBSCRIBE Contact: User-Agent: Windows RTC/1.0 Expires: 1800 Content-Length: 0 SIP/2.0 200 OK Via: SIP/2.0/TCP 10.140.13.178:9172;received-port=5060 To: sip:sudipta@10.140.13.149;tag=UKXBY32U8GYZBRWM CSeq: 1 SUBSCRIBE From: "i" ;tag=5a9e885b-5af7-45b4-ad41-33eb48ae6a99 Call-ID: 382d3998-db28-409d-b692-fedf56a685fe@10.140.13.178 Event: presence Expires: 1800 Content-Length: 0 REGISTER sip:10.140.13.149 SIP/2.0 Via: SIP/2.0/TCP 10.140.13.178:9172 From: ;tag=de061b7a-5964-43d5-a297-099e5d6e9796 To: Call-ID: b1737741-048e-4dab-9a03-4e910754f618@10.140.13.178 CSeq: 1 REGISTER Contact: ;methods="INVITE, MESSAGE, INFO, SUBSCRIBE, OPTIONS, BYE, CANCEL, NOTIFY, ACK" User-Agent: Windows RTC/1.0 Expires: 1200 Event: registration Allow-Events: presence Content-Length: 0 -- *********************************************** System Executive Mobile and Communication Tech. Scicom Infotech Pvt. Ltd. (Scicom) A - 67, Sector - 57 Noida - 201 301 UP ********************************************** _______________________________________________ simple mailing list simple@mailman.dynamicsoft.com http://mailman.dynamicsoft.com/mailman/listinfo/simple From simple-admin@mailman.dynamicsoft.com Fri Dec 6 05:35:02 2002 Received: from mail1.dynamicsoft.com (mail1.dynamicsoft.com [63.113.40.10]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id FAA01278 for ; Fri, 6 Dec 2002 05:35:02 -0500 (EST) Received: from mailman.dynamicsoft.com ([192.168.4.50]) by mail1.dynamicsoft.com (8.12.0.Beta7/8.12.0.Beta7) with ESMTP id gB6AZsQ4017338; Fri, 6 Dec 2002 05:35:54 -0500 (EST) Received: from mailman.dynamicsoft.com (localhost [127.0.0.1]) by mailman.dynamicsoft.com (8.9.3+Sun/8.9.3) with ESMTP id FAA17562; Fri, 6 Dec 2002 05:37:04 -0500 (EST) Received: from himalaya.scicmp.com ([203.200.79.36]) by mailman.dynamicsoft.com (8.9.3+Sun/8.9.3) with SMTP id FAA17546 for ; Fri, 6 Dec 2002 05:36:40 -0500 (EST) Received: from mx1.scicmp.com ([10.130.0.5]) by himalaya.scicmp.com (NAVGW 2.5.2.12) with SMTP id M2002120615562530354 for ; Fri, 06 Dec 2002 15:56:25 +0530 Received: from scicmp.com (kanchenjunga [10.140.13.178]) by mx1.scicmp.com (8.9.3/8.8.7) with ESMTP id QAA31898 for ; Fri, 6 Dec 2002 16:03:21 +0530 Message-ID: <3DF07BF8.3AFF5BBE@scicmp.com> From: Sudipta Ghosh Organization: Scicom Infotech Pvt. Ltd. (Scicom) X-Mailer: Mozilla 4.79 [en] (Windows NT 5.0; U) X-Accept-Language: en,pdf MIME-Version: 1.0 To: simple Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Subject: [Simple] Event Sender: simple-admin@mailman.dynamicsoft.com Errors-To: simple-admin@mailman.dynamicsoft.com X-BeenThere: simple@mailman.dynamicsoft.com X-Mailman-Version: 2.0 Precedence: bulk List-Help: List-Post: List-Subscribe: , List-Id: SIP for Presence List-Unsubscribe: , List-Archive: Date: Fri, 06 Dec 2002 15:59:12 +0530 Content-Transfer-Encoding: 7bit Hi, When IM Client is sending a SUBSCRIPTION request( to a offline user ) for presence notification to proxy,proxy sends response with 200 OK but adds a event header. Whats the meaning of it. In REGISTER request there is also a Event header. I am sending the packets.(got from MSN Messenger communication service) SUBSCRIBE sip:sudipta@10.140.13.149 SIP/2.0 Via: SIP/2.0/TCP 10.140.13.178:9172 From: "i" ;tag=5a9e885b-5af7-45b4-ad41-33eb48ae6a99 To: Call-ID: 382d3998-db28-409d-b692-fedf56a685fe@10.140.13.178 CSeq: 1 SUBSCRIBE Contact: User-Agent: Windows RTC/1.0 Expires: 1800 Content-Length: 0 SIP/2.0 200 OK Via: SIP/2.0/TCP 10.140.13.178:9172;received-port=5060 To: sip:sudipta@10.140.13.149;tag=UKXBY32U8GYZBRWM CSeq: 1 SUBSCRIBE From: "i" ;tag=5a9e885b-5af7-45b4-ad41-33eb48ae6a99 Call-ID: 382d3998-db28-409d-b692-fedf56a685fe@10.140.13.178 Event: presence Expires: 1800 Content-Length: 0 REGISTER sip:10.140.13.149 SIP/2.0 Via: SIP/2.0/TCP 10.140.13.178:9172 From: ;tag=de061b7a-5964-43d5-a297-099e5d6e9796 To: Call-ID: b1737741-048e-4dab-9a03-4e910754f618@10.140.13.178 CSeq: 1 REGISTER Contact: ;methods="INVITE, MESSAGE, INFO, SUBSCRIBE, OPTIONS, BYE, CANCEL, NOTIFY, ACK" User-Agent: Windows RTC/1.0 Expires: 1200 Event: registration Allow-Events: presence Content-Length: 0 -- *********************************************** System Executive Mobile and Communication Tech. Scicom Infotech Pvt. Ltd. (Scicom) A - 67, Sector - 57 Noida - 201 301 UP ********************************************** _______________________________________________ simple mailing list simple@mailman.dynamicsoft.com http://mailman.dynamicsoft.com/mailman/listinfo/simple From simple-admin@mailman.dynamicsoft.com Fri Dec 6 10:29:38 2002 Received: from mail1.dynamicsoft.com (mail1.dynamicsoft.com [63.113.40.10]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA10258 for ; Fri, 6 Dec 2002 10:29:38 -0500 (EST) Received: from mailman.dynamicsoft.com ([192.168.4.50]) by mail1.dynamicsoft.com (8.12.0.Beta7/8.12.0.Beta7) with ESMTP id gB6FUCQ4018175; Fri, 6 Dec 2002 10:30:12 -0500 (EST) Received: from mailman.dynamicsoft.com (localhost [127.0.0.1]) by mailman.dynamicsoft.com (8.9.3+Sun/8.9.3) with ESMTP id KAA18491; Fri, 6 Dec 2002 10:31:14 -0500 (EST) Received: from himalaya.scicmp.com ([203.200.79.36]) by mailman.dynamicsoft.com (8.9.3+Sun/8.9.3) with SMTP id JAA18299 for ; Fri, 6 Dec 2002 09:56:51 -0500 (EST) Received: from mx1.scicmp.com ([10.130.0.5]) by himalaya.scicmp.com (NAVGW 2.5.2.12) with SMTP id M2002120620270101991 ; Fri, 06 Dec 2002 20:27:01 +0530 Received: from scicmp.com (kanchenjunga [10.140.13.178]) by mx1.scicmp.com (8.9.3/8.8.7) with ESMTP id UAA03796; Fri, 6 Dec 2002 20:33:57 +0530 Message-ID: <3DF0BB65.1E041866@scicmp.com> From: Sudipta Ghosh Organization: Scicom Infotech Pvt. Ltd. (Scicom) X-Mailer: Mozilla 4.79 [en] (Windows NT 5.0; U) X-Accept-Language: en,pdf MIME-Version: 1.0 To: simple , sipforum Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Subject: [Simple] info Sender: simple-admin@mailman.dynamicsoft.com Errors-To: simple-admin@mailman.dynamicsoft.com X-BeenThere: simple@mailman.dynamicsoft.com X-Mailman-Version: 2.0 Precedence: bulk List-Help: List-Post: List-Subscribe: , List-Id: SIP for Presence List-Unsubscribe: , List-Archive: Date: Fri, 06 Dec 2002 20:29:49 +0530 Content-Transfer-Encoding: 7bit hi, is there any free/demo sip/simple server available so we can login through MSN Messenger communication server. sudipta -- *********************************************** System Executive Scicom Infotech Pvt. Ltd. (Scicom) A - 67, Sector - 57 Noida - 201 301 UP ********************************************** _______________________________________________ simple mailing list simple@mailman.dynamicsoft.com http://mailman.dynamicsoft.com/mailman/listinfo/simple From simple-admin@mailman.dynamicsoft.com Fri Dec 6 11:10:05 2002 Received: from mail1.dynamicsoft.com (mail1.dynamicsoft.com [63.113.40.10]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA12147 for ; Fri, 6 Dec 2002 11:10:04 -0500 (EST) Received: from mailman.dynamicsoft.com ([192.168.4.50]) by mail1.dynamicsoft.com (8.12.0.Beta7/8.12.0.Beta7) with ESMTP id gB6GAqQ4018450; Fri, 6 Dec 2002 11:10:53 -0500 (EST) Received: from mailman.dynamicsoft.com (localhost [127.0.0.1]) by mailman.dynamicsoft.com (8.9.3+Sun/8.9.3) with ESMTP id LAA18744; Fri, 6 Dec 2002 11:12:02 -0500 (EST) Received: from mail3.dynamicsoft.com (mail3.dynamicsoft.com [63.113.44.69]) by mailman.dynamicsoft.com (8.9.3+Sun/8.9.3) with ESMTP id LAA18733 for ; Fri, 6 Dec 2002 11:11:22 -0500 (EST) Received: from dynamicsoft.com ([63.113.47.242]) by mail3.dynamicsoft.com (8.12.1/8.12.1) with ESMTP id gB6GBMYH013130; Fri, 6 Dec 2002 11:11:25 -0500 (EST) Message-ID: <3DF0CC27.60907@dynamicsoft.com> From: Jonathan Rosenberg Organization: dynamicsoft User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.1) Gecko/20020826 X-Accept-Language: en-us, en MIME-Version: 1.0 To: Sudipta Ghosh CC: simple Subject: Re: [Simple] Event References: <3DF07BF8.3AFF5BBE@scicmp.com> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Sender: simple-admin@mailman.dynamicsoft.com Errors-To: simple-admin@mailman.dynamicsoft.com X-BeenThere: simple@mailman.dynamicsoft.com X-Mailman-Version: 2.0 Precedence: bulk List-Help: List-Post: List-Subscribe: , List-Id: SIP for Presence List-Unsubscribe: , List-Archive: Date: Fri, 06 Dec 2002 11:11:19 -0500 Content-Transfer-Encoding: 7bit answers inline. Sudipta Ghosh wrote: > Hi, > When IM Client is sending a SUBSCRIPTION request( to a offline user ) The request method is SUBSCRIBE, not SUBSCRIPTION. > for presence notification to proxy,proxy sends response with 200 OK but > adds a event header. The SUBSCRIBE request contains the Event header. It is not placed in the 200 OK response. It is, however, placed in the NOTIFY request generated by the presence server. > > Whats the meaning of it. SIP has a general events framework (RFC 3265). A particular resource, such as sip:jdrosen@dynamicsoft.com, can support multiple types of events, including presence, message waiting indicators, dialog events, etc. The Event header disambiguates the event types being requested of the resource. See RFC 3265 for a complete discussion. > > In REGISTER request there is also a Event header. No, there is no Event header in REGISTER. > I am sending the packets.(got from MSN Messenger communication service) This, to my knowledge, is an error in their implementation. It would be ignored by any SIP compliant registrar. -Jonathan R. -- Jonathan D. Rosenberg, Ph.D. 72 Eagle Rock Ave. Chief Scientist First Floor dynamicsoft East Hanover, NJ 07936 jdrosen@dynamicsoft.com FAX: (973) 952-5050 http://www.jdrosen.net PHONE: (973) 952-5000 http://www.dynamicsoft.com _______________________________________________ simple mailing list simple@mailman.dynamicsoft.com http://mailman.dynamicsoft.com/mailman/listinfo/simple From simple-admin@mailman.dynamicsoft.com Sun Dec 8 12:41:10 2002 Received: from mail1.dynamicsoft.com (mail1.dynamicsoft.com [63.113.40.10]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA05794 for ; Sun, 8 Dec 2002 12:41:09 -0500 (EST) Received: from mailman.dynamicsoft.com ([192.168.4.50]) by mail1.dynamicsoft.com (8.12.0.Beta7/8.12.0.Beta7) with ESMTP id gB8Hg4Q4023018; Sun, 8 Dec 2002 12:42:04 -0500 (EST) Received: from mailman.dynamicsoft.com (localhost [127.0.0.1]) by mailman.dynamicsoft.com (8.9.3+Sun/8.9.3) with ESMTP id MAA27271; Sun, 8 Dec 2002 12:43:11 -0500 (EST) Received: from sj-msg-core-3.cisco.com (sj-msg-core-3.cisco.com [171.70.157.152]) by mailman.dynamicsoft.com (8.9.3+Sun/8.9.3) with ESMTP id MAA27260 for ; Sun, 8 Dec 2002 12:42:23 -0500 (EST) Received: from mira-sjc5-9.cisco.com (IDENT:mirapoint@mira-sjc5-9.cisco.com [171.71.163.32]) by sj-msg-core-3.cisco.com (8.12.2/8.12.2) with ESMTP id gB8HfujS001743 for ; Sun, 8 Dec 2002 09:41:56 -0800 (PST) Received: from CJ650 (ssh-sjc-1.cisco.com [171.68.225.134]) by mira-sjc5-9.cisco.com (Mirapoint Messaging Server MOS 3.1.0.66-GA) with SMTP id EKF00105; Sun, 8 Dec 2002 09:42:38 -0800 (PST) From: "Cullen Jennings" To: Message-ID: MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook IMO, Build 9.0.2416 (9.0.2911.0) In-Reply-To: <200212051422.JAA12641@ietf.org> X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2600.0000 Importance: Normal Subject: [Simple] RE: I-D ACTION:draft-ietf-simple-presence-08.txt Sender: simple-admin@mailman.dynamicsoft.com Errors-To: simple-admin@mailman.dynamicsoft.com X-BeenThere: simple@mailman.dynamicsoft.com X-Mailman-Version: 2.0 Precedence: bulk List-Help: List-Post: List-Subscribe: , List-Id: SIP for Presence List-Unsubscribe: , List-Archive: Date: Sun, 8 Dec 2002 09:43:32 -0800 Content-Transfer-Encoding: 7bit I'm confused - is it version 8 or 9? all I can find is http://www.ietf.org/internet-drafts/draft-ietf-simple-presence-09.txt > -----Original Message----- > From: scoya@cnri.reston.va.us [mailto:scoya@cnri.reston.va.us]On Behalf > Of Internet-Drafts@ietf.org > Sent: Thursday, December 05, 2002 6:22 AM > To: IETF-Announce: > Cc: simple@mailman.dynamicsoft.com > Subject: I-D ACTION:draft-ietf-simple-presence-08.txt > > > 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 : A Presence Event Package for the Session > Initiation > Protocol (SIP) > Author(s) : J. Rosenberg > Filename : draft-ietf-simple-presence-08.txt > Pages : 26 > Date : 2002-12-4 > > This document describes the usage of the Session Initiation Protocol > (SIP) for subscriptions and notifications of presence. Presence is > defined as the willingness and ability of a user to communicate with > other users on the network. Historically, presence has been limited > to 'on-line' and 'off-line' indicators; the notion of presence here > is broader. Subscriptions and notifications of presence are supported > by defining an event package within the general SIP event > notification framework. This protocol is also compliant with the > Common Presence Profile (CPP) framework. > > A URL for this Internet-Draft is: > http://www.ietf.org/internet-drafts/draft-ietf-simple-presence-08.txt > > To remove yourself from the IETF Announcement list, send a message to > ietf-announce-request with the word unsubscribe in the body of > the message. > > 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-presence-08.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-presence-08.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. > _______________________________________________ simple mailing list simple@mailman.dynamicsoft.com http://mailman.dynamicsoft.com/mailman/listinfo/simple From simple-admin@mailman.dynamicsoft.com Sun Dec 8 16:41:54 2002 Received: from mail1.dynamicsoft.com (mail1.dynamicsoft.com [63.113.40.10]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA10333 for ; Sun, 8 Dec 2002 16:41:53 -0500 (EST) Received: from mailman.dynamicsoft.com ([192.168.4.50]) by mail1.dynamicsoft.com (8.12.0.Beta7/8.12.0.Beta7) with ESMTP id gB8LgvQ4023313; Sun, 8 Dec 2002 16:42:57 -0500 (EST) Received: from mailman.dynamicsoft.com (localhost [127.0.0.1]) by mailman.dynamicsoft.com (8.9.3+Sun/8.9.3) with ESMTP id QAA27914; Sun, 8 Dec 2002 16:44:04 -0500 (EST) Received: from sj-msg-core-1.cisco.com (sj-msg-core-1.cisco.com [171.71.163.11]) by mailman.dynamicsoft.com (8.9.3+Sun/8.9.3) with ESMTP id QAA27903 for ; Sun, 8 Dec 2002 16:43:30 -0500 (EST) Received: from mira-sjc5-9.cisco.com (IDENT:mirapoint@mira-sjc5-9.cisco.com [171.71.163.32]) by sj-msg-core-1.cisco.com (8.12.2/8.12.2) with ESMTP id gB8LhUFp001176 for ; Sun, 8 Dec 2002 13:43:30 -0800 (PST) Received: from cj14 (ssh-sjc-1.cisco.com [171.68.225.134]) by mira-sjc5-9.cisco.com (Mirapoint Messaging Server MOS 3.1.0.66-GA) with SMTP id EKR00122; Sun, 8 Dec 2002 13:43:52 -0800 (PST) From: "Cullen Jennings" To: Subject: RE: [Simple] RE: I-D ACTION:draft-ietf-simple-presence-08.txt Message-ID: MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook IMO, Build 9.0.2416 (9.0.2911.0) In-Reply-To: X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2600.0000 Importance: Normal Sender: simple-admin@mailman.dynamicsoft.com Errors-To: simple-admin@mailman.dynamicsoft.com X-BeenThere: simple@mailman.dynamicsoft.com X-Mailman-Version: 2.0 Precedence: bulk List-Help: List-Post: List-Subscribe: , List-Id: SIP for Presence List-Unsubscribe: , List-Archive: Date: Sun, 8 Dec 2002 13:46:31 -0800 Content-Transfer-Encoding: 7bit Sorry for the post without reading all the list - I see they were updated to a new version after this announcement. > -----Original Message----- > From: simple-admin@mailman.dynamicsoft.com > [mailto:simple-admin@mailman.dynamicsoft.com]On Behalf Of Cullen > Jennings > Sent: Sunday, December 08, 2002 9:44 AM > To: simple@mailman.dynamicsoft.com > Subject: [Simple] RE: I-D ACTION:draft-ietf-simple-presence-08.txt > > > > I'm confused - is it version 8 or 9? all I can find is > http://www.ietf.org/internet-drafts/draft-ietf-simple-presence-09.txt > > > > -----Original Message----- > > From: scoya@cnri.reston.va.us [mailto:scoya@cnri.reston.va.us]On Behalf > > Of Internet-Drafts@ietf.org > > Sent: Thursday, December 05, 2002 6:22 AM > > To: IETF-Announce: > > Cc: simple@mailman.dynamicsoft.com > > Subject: I-D ACTION:draft-ietf-simple-presence-08.txt > > > > > > 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 : A Presence Event Package for the Session > > Initiation > > Protocol (SIP) > > Author(s) : J. Rosenberg > > Filename : draft-ietf-simple-presence-08.txt > > Pages : 26 > > Date : 2002-12-4 > > > > This document describes the usage of the Session Initiation Protocol > > (SIP) for subscriptions and notifications of presence. Presence is > > defined as the willingness and ability of a user to communicate with > > other users on the network. Historically, presence has been limited > > to 'on-line' and 'off-line' indicators; the notion of presence here > > is broader. Subscriptions and notifications of presence are supported > > by defining an event package within the general SIP event > > notification framework. This protocol is also compliant with the > > Common Presence Profile (CPP) framework. > > > > A URL for this Internet-Draft is: > > http://www.ietf.org/internet-drafts/draft-ietf-simple-presence-08.txt > > > > To remove yourself from the IETF Announcement list, send a message to > > ietf-announce-request with the word unsubscribe in the body of > > the message. > > > > 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-presence-08.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-presence-08.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. > > > _______________________________________________ > simple mailing list > simple@mailman.dynamicsoft.com > http://mailman.dynamicsoft.com/mailman/listinfo/simple > _______________________________________________ simple mailing list simple@mailman.dynamicsoft.com http://mailman.dynamicsoft.com/mailman/listinfo/simple From simple-admin@mailman.dynamicsoft.com Mon Dec 9 01:27:00 2002 Received: from mail1.dynamicsoft.com (mail1.dynamicsoft.com [63.113.40.10]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id BAA19369 for ; Mon, 9 Dec 2002 01:27:00 -0500 (EST) Received: from mailman.dynamicsoft.com ([192.168.4.50]) by mail1.dynamicsoft.com (8.12.0.Beta7/8.12.0.Beta7) with ESMTP id gB96RtQ4023978; Mon, 9 Dec 2002 01:27:56 -0500 (EST) Received: from mailman.dynamicsoft.com (localhost [127.0.0.1]) by mailman.dynamicsoft.com (8.9.3+Sun/8.9.3) with ESMTP id BAA29485; Mon, 9 Dec 2002 01:29:05 -0500 (EST) Received: from himalaya.scicmp.com ([203.200.79.36]) by mailman.dynamicsoft.com (8.9.3+Sun/8.9.3) with SMTP id BAA29474 for ; Mon, 9 Dec 2002 01:28:17 -0500 (EST) Received: from mx1.scicmp.com ([10.130.0.5]) by himalaya.scicmp.com (NAVGW 2.5.2.12) with SMTP id M2002120911582706393 ; Mon, 09 Dec 2002 11:58:27 +0530 Received: from scicmp.com (kanchenjunga [10.140.13.178]) by mx1.scicmp.com (8.9.3/8.8.7) with ESMTP id MAA02766; Mon, 9 Dec 2002 12:05:10 +0530 Message-ID: <3DF438AC.9F077C05@scicmp.com> From: Sudipta Ghosh Organization: Scicom Infotech Pvt. Ltd. (Scicom) X-Mailer: Mozilla 4.79 [en] (Windows NT 5.0; U) X-Accept-Language: en,pdf MIME-Version: 1.0 To: simple , sipforum Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Subject: [Simple] msgr Sender: simple-admin@mailman.dynamicsoft.com Errors-To: simple-admin@mailman.dynamicsoft.com X-BeenThere: simple@mailman.dynamicsoft.com X-Mailman-Version: 2.0 Precedence: bulk List-Help: List-Post: List-Subscribe: , List-Id: SIP for Presence List-Unsubscribe: , List-Archive: Date: Mon, 09 Dec 2002 12:01:09 +0530 Content-Transfer-Encoding: 7bit Hi, MSN Messenger uses "msgr" tag in MESSAGE Request. What is that? sudipta Example MESSAGE sip:10.140.13.149:5060 SIP/2.0 Via: SIP/2.0/TCP 10.140.13.149:5060 Record-Route: Via: SIP/2.0/TCP 10.140.13.96:11138 From: "Client_A" ;tag=65056eff-f536-43dc-a795-947be959f714 To: ;tag=f6dfc966-ad80-4cea-b8bd-ce3de259b79a Call-ID: 89ef0faf-574f-4241-8a0f-9a3e4490a075@10.140.13.96 CSeq: 4 MESSAGE Route: Contact: User-Agent: Windows RTC/1.0 Content-Type: text/plain; charset=UTF-8;msgr=WAAtAE0ATQBTAC0ASQBNAC0ARgBvAHIAbQBhAHQAOgAgAEYATgA9AE0AUwAlADIAMABTAGgAZQBsAGwAJQAyADAARABsAGcAOwAgAEUARgA9ADsAIABDAE8APQAwADsAIABDAFMAPQAwADsAIABQAEYAPQAwAA0ACgANAAoA Content-Length: 18 -- *********************************************** System Executive Scicom Infotech Pvt. Ltd. (Scicom) A - 67, Sector - 57 Noida - 201 301 UP ********************************************** _______________________________________________ simple mailing list simple@mailman.dynamicsoft.com http://mailman.dynamicsoft.com/mailman/listinfo/simple From simple-admin@mailman.dynamicsoft.com Mon Dec 9 02:15:58 2002 Received: from mail1.dynamicsoft.com (mail1.dynamicsoft.com [63.113.40.10]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id CAA00114 for ; Mon, 9 Dec 2002 02:15:58 -0500 (EST) Received: from mailman.dynamicsoft.com ([192.168.4.50]) by mail1.dynamicsoft.com (8.12.0.Beta7/8.12.0.Beta7) with ESMTP id gB97GpQ4024102; Mon, 9 Dec 2002 02:16:51 -0500 (EST) Received: from mailman.dynamicsoft.com (localhost [127.0.0.1]) by mailman.dynamicsoft.com (8.9.3+Sun/8.9.3) with ESMTP id CAA29642; Mon, 9 Dec 2002 02:18:03 -0500 (EST) Received: from computer.mywwwserver.com ([66.78.35.28]) by mailman.dynamicsoft.com (8.9.3+Sun/8.9.3) with ESMTP id CAA29631 for ; Mon, 9 Dec 2002 02:17:39 -0500 (EST) Received: from ptil-146-95-del.primus-india.net ([210.7.95.146] helo=spgwin1) by computer.mywwwserver.com with smtp (Exim 3.36 #1) id 18LIAZ-0000nE-00; Mon, 09 Dec 2002 02:17:35 -0500 Message-ID: <002801c29f53$23777b10$925f07d2@spgwin1> From: "Hemant Kumar" To: "Sudipta Ghosh" , "simple" , "sipforum" References: <3DF438AC.9F077C05@scicmp.com> Subject: Re: [Simple] msgr MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 5.00.2919.6700 X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2919.6700 X-AntiAbuse: This header was added to track abuse, please include it with any abuse report X-AntiAbuse: Primary Hostname - computer.mywwwserver.com X-AntiAbuse: Original Domain - mailman.dynamicsoft.com X-AntiAbuse: Originator/Caller UID/GID - [0 0] / [0 0] X-AntiAbuse: Sender Address Domain - spgsolutions.com Sender: simple-admin@mailman.dynamicsoft.com Errors-To: simple-admin@mailman.dynamicsoft.com X-BeenThere: simple@mailman.dynamicsoft.com X-Mailman-Version: 2.0 Precedence: bulk List-Help: List-Post: List-Subscribe: , List-Id: SIP for Presence List-Unsubscribe: , List-Archive: Date: Mon, 9 Dec 2002 12:48:10 +0530 Content-Transfer-Encoding: 7bit If you'll look at the value of this tag in different messages, you'll find out the value is "WAAtAE0ATQBTAC0ASQBNAC0ARgBvAHIAbQBhAHQAOgAgAEYATgA9AE0AUwAlADIA MABTAGgAZQBsAGwAJQAyADAARABsAGcAOwAgAEUARgA9ADsAIABDAE8APQAwADsA IABDAFMAPQAwADsAIABQAEYAPQAwAA0ACgANAAoA" and it is same always (well atleast all the messages I saw, it was same). So, I think it is Unique String in charset, just make sure that this message is from MSN Messenger. rgds, /hem -- Hemant Kumar, Project Manager, SPG Solutions,LLC B-372, Meera Bagh, Paschim Vihar, New Delhi - 110063, Phone:+91.11.25271704 Fax:+91.11.25286949 Email:hkumar@spgsolutions.com ----- Original Message ----- From: "Sudipta Ghosh" To: "simple" ; "sipforum" Sent: Monday, December 09, 2002 12:01 PM Subject: [Simple] msgr > Hi, > MSN Messenger uses "msgr" tag in MESSAGE Request. > What is that? > sudipta > > Example > > > MESSAGE sip:10.140.13.149:5060 SIP/2.0 > Via: SIP/2.0/TCP 10.140.13.149:5060 > Record-Route: > > Via: SIP/2.0/TCP 10.140.13.96:11138 > From: "Client_A" > ;tag=65056eff-f536-43dc-a795-947be959f714 > To: > ;tag=f6dfc966-ad80-4cea-b8bd-ce3de259b79a > Call-ID: 89ef0faf-574f-4241-8a0f-9a3e4490a075@10.140.13.96 > CSeq: 4 MESSAGE > Route: > Contact: > User-Agent: Windows RTC/1.0 > Content-Type: text/plain; > charset=UTF-8;msgr=WAAtAE0ATQBTAC0ASQBNAC0ARgBvAHIAbQBhAHQAOgAgAEYATgA9AE0AU wAlADIAMABTAGgAZQBsAGwAJQAyADAARABsAGcAOwAgAEUARgA9ADsAIABDAE8APQAwADsAIABDA FMAPQAwADsAIABQAEYAPQAwAA0ACgANAAoA > > Content-Length: 18 > > > -- > *********************************************** > System Executive > Scicom Infotech Pvt. Ltd. (Scicom) > A - 67, Sector - 57 > Noida - 201 301 > UP > ********************************************** > > > _______________________________________________ > simple mailing list > simple@mailman.dynamicsoft.com > http://mailman.dynamicsoft.com/mailman/listinfo/simple > > _______________________________________________ simple mailing list simple@mailman.dynamicsoft.com http://mailman.dynamicsoft.com/mailman/listinfo/simple From simple-admin@mailman.dynamicsoft.com Mon Dec 9 08:04:33 2002 Received: from mail1.dynamicsoft.com (mail1.dynamicsoft.com [63.113.40.10]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA07511 for ; Mon, 9 Dec 2002 08:04:32 -0500 (EST) Received: from mailman.dynamicsoft.com ([192.168.4.50]) by mail1.dynamicsoft.com (8.12.0.Beta7/8.12.0.Beta7) with ESMTP id gB9D5cRh000677; Mon, 9 Dec 2002 08:05:38 -0500 (EST) Received: from mailman.dynamicsoft.com (localhost [127.0.0.1]) by mailman.dynamicsoft.com (8.9.3+Sun/8.9.3) with ESMTP id IAA00867; Mon, 9 Dec 2002 08:06:51 -0500 (EST) Received: from ietf.org (odin.ietf.org [132.151.1.176]) by mailman.dynamicsoft.com (8.9.3+Sun/8.9.3) with ESMTP id IAA00840 for ; Mon, 9 Dec 2002 08:05:52 -0500 (EST) Received: from CNRI.Reston.VA.US (localhost [127.0.0.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA07242; Mon, 9 Dec 2002 08:02:59 -0500 (EST) Message-Id: <200212091302.IAA07242@ietf.org> Mime-Version: 1.0 Content-Type: Multipart/Mixed; Boundary="NextPart" To: IETF-Announce: ; Cc: simple@mailman.dynamicsoft.com From: Internet-Drafts@ietf.org Reply-to: Internet-Drafts@ietf.org Subject: [Simple] I-D ACTION:draft-ietf-simple-winfo-package-04.txt Sender: simple-admin@mailman.dynamicsoft.com Errors-To: simple-admin@mailman.dynamicsoft.com X-BeenThere: simple@mailman.dynamicsoft.com X-Mailman-Version: 2.0 Precedence: bulk List-Help: List-Post: List-Subscribe: , List-Id: SIP for Presence List-Unsubscribe: , List-Archive: Date: Mon, 09 Dec 2002 08:02:58 -0500 --NextPart 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 : A Watcher Information Event Template-Package for the Session Initiation Protocol (SIP) Author(s) : J. Rosenberg Filename : draft-ietf-simple-winfo-package-04.txt Pages : 19 Date : 2002-12-6 This document defines the watcher information template-package for the SIP event framework. Watcher information refers to the set of users subscribed to a particular resource within a particular event package. Watcher information changes dynamically as users subscribe, unsubscribe, are approved, or are rejected. A user can subscribe to this information, and therefore learn about changes to it. This event package is a template-package because it can be applied to any event package, including itself. A URL for this Internet-Draft is: http://www.ietf.org/internet-drafts/draft-ietf-simple-winfo-package-04.txt To remove yourself from the IETF Announcement list, send a message to ietf-announce-request with the word unsubscribe in the body of the message. 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-winfo-package-04.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-winfo-package-04.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. --NextPart Content-Type: Multipart/Alternative; Boundary="OtherAccess" --OtherAccess Content-Type: Message/External-body; access-type="mail-server"; server="mailserv@ietf.org" Content-Type: text/plain Content-ID: <2002-12-6140333.I-D@ietf.org> ENCODING mime FILE /internet-drafts/draft-ietf-simple-winfo-package-04.txt --OtherAccess Content-Type: Message/External-body; name="draft-ietf-simple-winfo-package-04.txt"; site="ftp.ietf.org"; access-type="anon-ftp"; directory="internet-drafts" Content-Type: text/plain Content-ID: <2002-12-6140333.I-D@ietf.org> --OtherAccess-- --NextPart-- _______________________________________________ simple mailing list simple@mailman.dynamicsoft.com http://mailman.dynamicsoft.com/mailman/listinfo/simple From simple-admin@mailman.dynamicsoft.com Mon Dec 9 08:05:14 2002 Received: from mail1.dynamicsoft.com (mail1.dynamicsoft.com [63.113.40.10]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA07564 for ; Mon, 9 Dec 2002 08:05:14 -0500 (EST) Received: from mailman.dynamicsoft.com ([192.168.4.50]) by mail1.dynamicsoft.com (8.12.0.Beta7/8.12.0.Beta7) with ESMTP id gB9D4sRh000663; Mon, 9 Dec 2002 08:04:54 -0500 (EST) Received: from mailman.dynamicsoft.com (localhost [127.0.0.1]) by mailman.dynamicsoft.com (8.9.3+Sun/8.9.3) with ESMTP id IAA00851; Mon, 9 Dec 2002 08:06:04 -0500 (EST) Received: from ietf.org (odin.ietf.org [132.151.1.176]) by mailman.dynamicsoft.com (8.9.3+Sun/8.9.3) with ESMTP id IAA00835 for ; Mon, 9 Dec 2002 08:05:47 -0500 (EST) Received: from CNRI.Reston.VA.US (localhost [127.0.0.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA07223; Mon, 9 Dec 2002 08:02:53 -0500 (EST) Message-Id: <200212091302.IAA07223@ietf.org> Mime-Version: 1.0 Content-Type: Multipart/Mixed; Boundary="NextPart" To: IETF-Announce: ; Cc: simple@mailman.dynamicsoft.com From: Internet-Drafts@ietf.org Reply-to: Internet-Drafts@ietf.org Subject: [Simple] I-D ACTION:draft-ietf-simple-presence-09.txt Sender: simple-admin@mailman.dynamicsoft.com Errors-To: simple-admin@mailman.dynamicsoft.com X-BeenThere: simple@mailman.dynamicsoft.com X-Mailman-Version: 2.0 Precedence: bulk List-Help: List-Post: List-Subscribe: , List-Id: SIP for Presence List-Unsubscribe: , List-Archive: Date: Mon, 09 Dec 2002 08:02:52 -0500 --NextPart 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 : A Presence Event Package for the Session Initiation Protocol (SIP) Author(s) : J. Rosenberg Filename : draft-ietf-simple-presence-09.txt Pages : 26 Date : 2002-12-6 This document describes the usage of the Session Initiation Protocol (SIP) for subscriptions and notifications of presence. Presence is defined as the willingness and ability of a user to communicate with other users on the network. Historically, presence has been limited to 'on-line' and 'off-line' indicators; the notion of presence here is broader. Subscriptions and notifications of presence are supported by defining an event package within the general SIP event notification framework. This protocol is also compliant with the Common Presence Profile (CPP) framework. A URL for this Internet-Draft is: http://www.ietf.org/internet-drafts/draft-ietf-simple-presence-09.txt To remove yourself from the IETF Announcement list, send a message to ietf-announce-request with the word unsubscribe in the body of the message. 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-presence-09.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-presence-09.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. --NextPart Content-Type: Multipart/Alternative; Boundary="OtherAccess" --OtherAccess Content-Type: Message/External-body; access-type="mail-server"; server="mailserv@ietf.org" Content-Type: text/plain Content-ID: <2002-12-6140324.I-D@ietf.org> ENCODING mime FILE /internet-drafts/draft-ietf-simple-presence-09.txt --OtherAccess Content-Type: Message/External-body; name="draft-ietf-simple-presence-09.txt"; site="ftp.ietf.org"; access-type="anon-ftp"; directory="internet-drafts" Content-Type: text/plain Content-ID: <2002-12-6140324.I-D@ietf.org> --OtherAccess-- --NextPart-- _______________________________________________ simple mailing list simple@mailman.dynamicsoft.com http://mailman.dynamicsoft.com/mailman/listinfo/simple From simple-admin@mailman.dynamicsoft.com Mon Dec 9 09:06:00 2002 Received: from mail1.dynamicsoft.com (mail1.dynamicsoft.com [63.113.40.10]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA09913 for ; Mon, 9 Dec 2002 09:06:00 -0500 (EST) Received: from mailman.dynamicsoft.com ([192.168.4.50]) by mail1.dynamicsoft.com (8.12.0.Beta7/8.12.0.Beta7) with ESMTP id gB9E5vRh000995; Mon, 9 Dec 2002 09:05:57 -0500 (EST) Received: from mailman.dynamicsoft.com (localhost [127.0.0.1]) by mailman.dynamicsoft.com (8.9.3+Sun/8.9.3) with ESMTP id JAA01143; Mon, 9 Dec 2002 09:07:03 -0500 (EST) Received: from mail.unboundtech.com (tetsuo.unboundtech.com [66.150.129.229]) by mailman.dynamicsoft.com (8.9.3+Sun/8.9.3) with ESMTP id JAA01132 for ; Mon, 9 Dec 2002 09:06:38 -0500 (EST) Received: from Peace (ool-18bd1a09.dyn.optonline.net [24.189.26.9]) by mail.unboundtech.com (Postfix) with ESMTP id 6644088B88; Mon, 9 Dec 2002 08:06:38 -0600 (CST) From: "shanti" To: "simple" , "sipforum" Message-ID: MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook IMO, Build 9.0.2416 (9.0.2910.0) X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1106 In-Reply-To: <002801c29f53$23777b10$925f07d2@spgwin1> Importance: Normal Subject: [Simple] SIP MESSAGE with MSN Sender: simple-admin@mailman.dynamicsoft.com Errors-To: simple-admin@mailman.dynamicsoft.com X-BeenThere: simple@mailman.dynamicsoft.com X-Mailman-Version: 2.0 Precedence: bulk List-Help: List-Post: List-Subscribe: , List-Id: SIP for Presence List-Unsubscribe: , List-Archive: Date: Mon, 9 Dec 2002 09:06:37 -0500 Content-Transfer-Encoding: 7bit hi, When I send a SIP MESSAGE request to MSN client, it responds with 200 ok but doesnot display the message . Following is the message am sending, and the response received from the MSN client. MESSAGE sip:kviswa@abc.com SIP/2.0 CSeq: 1 MESSAGE Call-Id: 1039218960404 From: ;tag=1093 To: Via: SIP/2.0/UDP 192.168.123.159:2000 Content-Type: application/text-plain Contact: Content-Length: 18 Hello Thread-5:---------------------------------------- Thread-5:from = 127.0.0.1:3883 to = 192.168.123.159:2000 message = SIP/2.0 200 OK Via: SIP/2.0/UDP 192.168.123.159:2000;branch=z9hG4bKad3693a4af1fd0c172f5a3cd2da61f43 From: ;tag=1093 To: ;tag=156b140c-b8bc-431c-8416-467ef5b4c6f8 Call-Id: 1039218960404 CSeq: 1 MESSAGE Contact: User-Agent: Windows RTC/1.0 Content-Length: 0 Your help on this is much appreciated. thanks, shanti _______________________________________________ simple mailing list simple@mailman.dynamicsoft.com http://mailman.dynamicsoft.com/mailman/listinfo/simple From simple-admin@mailman.dynamicsoft.com Mon Dec 9 09:28:49 2002 Received: from mail1.dynamicsoft.com (mail1.dynamicsoft.com [63.113.40.10]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA10723 for ; Mon, 9 Dec 2002 09:28:49 -0500 (EST) Received: from mailman.dynamicsoft.com ([192.168.4.50]) by mail1.dynamicsoft.com (8.12.0.Beta7/8.12.0.Beta7) with ESMTP id gB9ETpRh001164; Mon, 9 Dec 2002 09:29:51 -0500 (EST) Received: from mailman.dynamicsoft.com (localhost [127.0.0.1]) by mailman.dynamicsoft.com (8.9.3+Sun/8.9.3) with ESMTP id JAA01243; Mon, 9 Dec 2002 09:31:03 -0500 (EST) Received: from m3001.hostcentric.net (m3001.hostcentric.net [216.157.79.237]) by mailman.dynamicsoft.com (8.9.3+Sun/8.9.3) with SMTP id JAA01232 for ; Mon, 9 Dec 2002 09:30:38 -0500 (EST) Received: (qmail 29690 invoked by alias); 9 Dec 2002 14:30:40 -0000 Received: from unknown (HELO indigosw.com) (217.136.220.14) by 0 with SMTP; 9 Dec 2002 14:30:40 -0000 Message-ID: <3DF4A856.5000203@indigosw.com> From: Torrey Searle Organization: Indigo Software, Inc. User-Agent: Mozilla/5.0 (X11; U; Linux i686; fr-FR; rv:1.0.0) Gecko/20020529 X-Accept-Language: en-us MIME-Version: 1.0 To: shanti CC: simple , sipforum Subject: Re: [Simple] SIP MESSAGE with MSN References: Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 8bit Sender: simple-admin@mailman.dynamicsoft.com Errors-To: simple-admin@mailman.dynamicsoft.com X-BeenThere: simple@mailman.dynamicsoft.com X-Mailman-Version: 2.0 Precedence: bulk List-Help: List-Post: List-Subscribe: , List-Id: SIP for Presence List-Unsubscribe: , List-Archive: Date: Mon, 09 Dec 2002 15:27:34 +0100 Content-Transfer-Encoding: 8bit When MSN doesn't understand the content type, responds 200 OK w/o displaying the message. Try sending a content type of Content-Type: text/plain instead Torrey Searle Indigo Software shanti a écrit: >hi, > >When I send a SIP MESSAGE request to MSN client, it responds with 200 ok but >doesnot display the message . > >Following is the message am sending, and the response received from the MSN >client. > > >MESSAGE sip:kviswa@abc.com SIP/2.0 >CSeq: 1 MESSAGE >Call-Id: 1039218960404 >From: ;tag=1093 >To: >Via: SIP/2.0/UDP 192.168.123.159:2000 >Content-Type: application/text-plain >Contact: >Content-Length: 18 > >Hello > >Thread-5:---------------------------------------- >Thread-5:from = 127.0.0.1:3883 > to = 192.168.123.159:2000 > message = SIP/2.0 200 OK >Via: SIP/2.0/UDP >192.168.123.159:2000;branch=z9hG4bKad3693a4af1fd0c172f5a3cd2da61f43 >From: ;tag=1093 >To: ;tag=156b140c-b8bc-431c-8416-467ef5b4c6f8 >Call-Id: 1039218960404 >CSeq: 1 MESSAGE >Contact: >User-Agent: Windows RTC/1.0 >Content-Length: 0 > > >Your help on this is much appreciated. > >thanks, >shanti > > >_______________________________________________ >simple mailing list >simple@mailman.dynamicsoft.com >http://mailman.dynamicsoft.com/mailman/listinfo/simple > > _______________________________________________ simple mailing list simple@mailman.dynamicsoft.com http://mailman.dynamicsoft.com/mailman/listinfo/simple From simple-admin@mailman.dynamicsoft.com Mon Dec 9 11:13:15 2002 Received: from mail1.dynamicsoft.com (mail1.dynamicsoft.com [63.113.40.10]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA15711 for ; Mon, 9 Dec 2002 11:13:15 -0500 (EST) Received: from mailman.dynamicsoft.com ([192.168.4.50]) by mail1.dynamicsoft.com (8.12.0.Beta7/8.12.0.Beta7) with ESMTP id gB9GDuRh001671; Mon, 9 Dec 2002 11:13:57 -0500 (EST) Received: from mailman.dynamicsoft.com (localhost [127.0.0.1]) by mailman.dynamicsoft.com (8.9.3+Sun/8.9.3) with ESMTP id LAA01606; Mon, 9 Dec 2002 11:15:05 -0500 (EST) Received: from relay2.clb.oleane.net (relay2.clb.oleane.net [213.56.31.22]) by mailman.dynamicsoft.com (8.9.3+Sun/8.9.3) with ESMTP id LAA01593 for ; Mon, 9 Dec 2002 11:14:14 -0500 (EST) Received: from oleane (upper-side.rain.fr [194.250.212.114]) by relay2.clb.oleane.net with SMTP id gB9GEBPw028530 for ; Mon, 9 Dec 2002 17:14:15 +0100 Message-ID: <026b01c29f9f$0a8e2760$0601a8c0@oleane.com> From: "Peter Lewis" To: MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_NextPart_000_0268_01C29FA7.69DDE5E0" X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 5.00.2615.200 X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2615.200 Subject: [Simple] International SIP Conference Sender: simple-admin@mailman.dynamicsoft.com Errors-To: simple-admin@mailman.dynamicsoft.com X-BeenThere: simple@mailman.dynamicsoft.com X-Mailman-Version: 2.0 Precedence: bulk List-Help: List-Post: List-Subscribe: , List-Id: SIP for Presence List-Unsubscribe: , List-Archive: Date: Mon, 9 Dec 2002 17:21:30 +0100 This is a multi-part message in MIME format. ------=_NextPart_000_0268_01C29FA7.69DDE5E0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable A Free SIP Server in the International SIP Conference Registration = Package=20 Each participant to the International SIP'03 conference will be given = iptel.org's SIP server in his registration package. It is a free SIP = server recently released to the community. It will be in a form of a = credit-card-size CD with an enclosed description.=20 iptel.org is a non-profit knowledge-advancement company under umbrella = of FhG (Germany's reasearch network, non-profit too). All other outcomes = (currently, on-line knowledge base and the SIP server) are freely = available to the community at no cost. Please get more details at: = http://www.iptel.org=20 Get all informations on the International SIP event at: = http://www.upperside.fr/intersip03/sip03intro.htm=20 ------=_NextPart_000_0268_01C29FA7.69DDE5E0 Content-Type: text/html; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable
A Free SIP = Server in the=20 International SIP Conference Registration Package =

Each=20 participant to the International SIP'03 conference will be given = iptel.org's SIP=20 server in his registration package. It is a free SIP server recently = released to=20 the community. It will be in a form of a credit-card-size CD with an = enclosed=20 description.

iptel.org is a non-profit = knowledge-advancement=20 company under umbrella of FhG (Germany's reasearch network, non-profit = too). All=20 other outcomes (currently, on-line knowledge base and the SIP server) = are freely=20 available to the community at no cost. Please get more details at: http://www.iptel.org

Get all=20 informations on the International SIP event at: http://www.upp= erside.fr/intersip03/sip03intro.htm=20
------=_NextPart_000_0268_01C29FA7.69DDE5E0-- _______________________________________________ simple mailing list simple@mailman.dynamicsoft.com http://mailman.dynamicsoft.com/mailman/listinfo/simple From simple-admin@mailman.dynamicsoft.com Mon Dec 9 14:13:28 2002 Received: from mail1.dynamicsoft.com (mail1.dynamicsoft.com [63.113.40.10]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA25958 for ; Mon, 9 Dec 2002 14:13:28 -0500 (EST) Received: from mailman.dynamicsoft.com ([192.168.4.50]) by mail1.dynamicsoft.com (8.12.0.Beta7/8.12.0.Beta7) with ESMTP id gB9JASRh002471; Mon, 9 Dec 2002 14:10:28 -0500 (EST) Received: from mailman.dynamicsoft.com (localhost [127.0.0.1]) by mailman.dynamicsoft.com (8.9.3+Sun/8.9.3) with ESMTP id OAA02199; Mon, 9 Dec 2002 14:10:09 -0500 (EST) Received: from d12lmsgate-3.de.ibm.com (d12lmsgate-3.de.ibm.com [194.196.100.236]) by mailman.dynamicsoft.com (8.9.3+Sun/8.9.3) with ESMTP id OAA02186 for ; Mon, 9 Dec 2002 14:09:06 -0500 (EST) Received: from d12relay02.de.ibm.com (d12relay02.de.ibm.com [9.165.215.23]) by d12lmsgate-3.de.ibm.com (8.12.3/8.12.3) with ESMTP id gB9J97C3086616 for ; Mon, 9 Dec 2002 20:09:07 +0100 Received: from d10ml001.telaviv.ibm.com (d10ml001.telaviv.ibm.com [9.148.216.55]) by d12relay02.de.ibm.com (8.12.3/NCO/VER6.4) with ESMTP id gB9J96cO055290; Mon, 9 Dec 2002 20:09:07 +0100 To: Cc: Tony Hansen MIME-Version: 1.0 X-Mailer: Lotus Notes Release 6.0 September 26, 2002 Message-ID: From: "Avshalom Houri" X-MIMETrack: Serialize by Router on D10ML001/10/M/IBM(Release 5.0.9a |January 7, 2002) at 09/12/2002 21:09:07, Serialize complete at 09/12/2002 21:09:07 Content-Type: multipart/alternative; boundary="=_alternative 00692688C2256C8A_=" Subject: [Simple] SIMPLE system architecture draft Sender: simple-admin@mailman.dynamicsoft.com Errors-To: simple-admin@mailman.dynamicsoft.com X-BeenThere: simple@mailman.dynamicsoft.com X-Mailman-Version: 2.0 Precedence: bulk List-Help: List-Post: List-Subscribe: , List-Id: SIP for Presence List-Unsubscribe: , List-Archive: Date: Mon, 9 Dec 2002 21:08:55 +0200 This is a multipart message in MIME format. --=_alternative 00692688C2256C8A_= Content-Type: text/plain; charset="US-ASCII" We are starting to work on an architecture document for SIMPLE. The architecture document will specify how a complete presence and IM system can be built, based on SIMPLE and other IETF technologies. It will put everything together, discussing the servers involved, the security mechanisms, the call flows, etc. The idea is that someone who is not an expert in the IETF protocols can read this document and understand how the IETF protocols can be used for building a complete system and how it should work. We would appreciate any suggestions for items to be included in the outline of the document. We would like to post the outline before the holiday breaks begin. Thanks Tony Hansen & Avshalom Houri --=_alternative 00692688C2256C8A_= Content-Type: text/html; charset="US-ASCII"
We are starting to work on an architecture document for SIMPLE. The
architecture document will specify how a complete presence and IM system
can be built, based on SIMPLE and other IETF technologies. It will put
everything together, discussing the servers involved, the security
mechanisms, the call flows, etc.

The idea is that someone who is not an expert in the IETF protocols can
read this document and understand how the IETF protocols can be used for
building a complete system and how it should work.

We would appreciate any suggestions for items to be included in the
outline of the document. We would like to post the outline before the
holiday breaks begin.

Thanks
                Tony Hansen & Avshalom Houri
 --=_alternative 00692688C2256C8A_=-- _______________________________________________ simple mailing list simple@mailman.dynamicsoft.com http://mailman.dynamicsoft.com/mailman/listinfo/simple From simple-admin@mailman.dynamicsoft.com Tue Dec 10 07:44:56 2002 Received: from mail1.dynamicsoft.com (mail1.dynamicsoft.com [63.113.40.10]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA05141 for ; Tue, 10 Dec 2002 07:44:55 -0500 (EST) Received: from mailman.dynamicsoft.com ([192.168.4.50]) by mail1.dynamicsoft.com (8.12.0.Beta7/8.12.0.Beta7) with ESMTP id gBACjtRh005056; Tue, 10 Dec 2002 07:45:55 -0500 (EST) Received: from mailman.dynamicsoft.com (localhost [127.0.0.1]) by mailman.dynamicsoft.com (8.9.3+Sun/8.9.3) with ESMTP id HAA05221; Tue, 10 Dec 2002 07:47:03 -0500 (EST) Received: from himalaya.scicmp.com ([203.200.79.36]) by mailman.dynamicsoft.com (8.9.3+Sun/8.9.3) with SMTP id HAA05210 for ; Tue, 10 Dec 2002 07:46:16 -0500 (EST) Received: from mx1.scicmp.com ([10.130.0.5]) by himalaya.scicmp.com (NAVGW 2.5.2.12) with SMTP id M2002121018163915051 for ; Tue, 10 Dec 2002 18:16:39 +0530 Received: from scicmp.com (kanchenjunga [10.140.13.178]) by mx1.scicmp.com (8.9.3/8.8.7) with ESMTP id SAA03109 for ; Tue, 10 Dec 2002 18:23:24 +0530 Message-ID: <3DF5E2D4.E158291E@scicmp.com> From: Sudipta Ghosh Organization: Scicom Infotech Pvt. Ltd. (Scicom) X-Mailer: Mozilla 4.79 [en] (Windows NT 5.0; U) X-Accept-Language: en,pdf MIME-Version: 1.0 To: simple Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Subject: [Simple] client Sender: simple-admin@mailman.dynamicsoft.com Errors-To: simple-admin@mailman.dynamicsoft.com X-BeenThere: simple@mailman.dynamicsoft.com X-Mailman-Version: 2.0 Precedence: bulk List-Help: List-Post: List-Subscribe: , List-Id: SIP for Presence List-Unsubscribe: , List-Archive: Date: Tue, 10 Dec 2002 18:19:25 +0530 Content-Transfer-Encoding: 7bit hi, what r the sip/simple enabled client available now a days. sudipta -- *********************************************** System Executive Scicom Infotech Pvt. Ltd. (Scicom) A - 67, Sector - 57 Noida - 201 301 UP ********************************************** _______________________________________________ simple mailing list simple@mailman.dynamicsoft.com http://mailman.dynamicsoft.com/mailman/listinfo/simple From simple-admin@mailman.dynamicsoft.com Tue Dec 10 10:08:07 2002 Received: from mail1.dynamicsoft.com (mail1.dynamicsoft.com [63.113.40.10]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA09401 for ; Tue, 10 Dec 2002 10:08:07 -0500 (EST) Received: from mailman.dynamicsoft.com ([192.168.4.50]) by mail1.dynamicsoft.com (8.12.0.Beta7/8.12.0.Beta7) with ESMTP id gBAF8tRh005613; Tue, 10 Dec 2002 10:08:55 -0500 (EST) Received: from mailman.dynamicsoft.com (localhost [127.0.0.1]) by mailman.dynamicsoft.com (8.9.3+Sun/8.9.3) with ESMTP id KAA05712; Tue, 10 Dec 2002 10:10:04 -0500 (EST) Received: from dyn-tx-arch-crash.dfw.dynamicsoft.com (dyn-tx-arch-crash.dfw.dynamicsoft.com [63.110.3.64]) by mailman.dynamicsoft.com (8.9.3+Sun/8.9.3) with ESMTP id KAA05699 for ; Tue, 10 Dec 2002 10:09:44 -0500 (EST) Received: from RjS.localdomain (localhost.localdomain [127.0.0.1]) by dyn-tx-arch-crash.dfw.dynamicsoft.com (8.11.6/8.11.6) with ESMTP id gBAF9kI19239 for ; Tue, 10 Dec 2002 09:09:46 -0600 From: Robert Sparks To: simple In-Reply-To: <3DF5E2D4.E158291E@scicmp.com> References: <3DF5E2D4.E158291E@scicmp.com> Content-Type: text/plain Content-Transfer-Encoding: 7bit X-Mailer: Ximian Evolution 1.0.8 (1.0.8-10) Message-Id: <1039532891.943.26.camel@RjS.localdomain> Mime-Version: 1.0 Subject: [Simple] Please take implementation questions to sip-implementors Sender: simple-admin@mailman.dynamicsoft.com Errors-To: simple-admin@mailman.dynamicsoft.com X-BeenThere: simple@mailman.dynamicsoft.com X-Mailman-Version: 2.0 Precedence: bulk List-Help: List-Post: List-Subscribe: , List-Id: SIP for Presence List-Unsubscribe: , List-Archive: Date: 10 Dec 2002 09:08:11 -0600 Content-Transfer-Encoding: 7bit Folks - There's a list specifically set up to discuss SIP and SIMPLE implementation questions like how to work with a particular vendor's product or to canvas who has implemented a particular feature. The list is sip-implementors@cs.columbia.edu. Per the instructions at http://www.cs.columbia.edu/~hgs/sip/list.html, you can subscribe by sending email to sip-implementors-request@cs.columbia.edu with "subscribe sip-implementors" in the body or using the web interface at http://lists.cs.columbia.edu/mailman/listinfo/sip-implementors Please take the implementation questions there and refrain from posting them to this list. Thanks, RjS _______________________________________________ simple mailing list simple@mailman.dynamicsoft.com http://mailman.dynamicsoft.com/mailman/listinfo/simple From simple-admin@mailman.dynamicsoft.com Tue Dec 10 10:28:42 2002 Received: from mail1.dynamicsoft.com (mail1.dynamicsoft.com [63.113.40.10]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA10477 for ; Tue, 10 Dec 2002 10:28:42 -0500 (EST) Received: from mailman.dynamicsoft.com ([192.168.4.50]) by mail1.dynamicsoft.com (8.12.0.Beta7/8.12.0.Beta7) with ESMTP id gBAFOqRh005760; Tue, 10 Dec 2002 10:24:52 -0500 (EST) Received: from mailman.dynamicsoft.com (localhost [127.0.0.1]) by mailman.dynamicsoft.com (8.9.3+Sun/8.9.3) with ESMTP id KAA05808; Tue, 10 Dec 2002 10:26:03 -0500 (EST) Received: from himalaya.scicmp.com ([203.200.79.36]) by mailman.dynamicsoft.com (8.9.3+Sun/8.9.3) with SMTP id DAA04526 for ; Tue, 10 Dec 2002 03:41:08 -0500 (EST) Received: from mx1.scicmp.com ([10.130.0.5]) by himalaya.scicmp.com (NAVGW 2.5.2.12) with SMTP id M2002121014111306096 ; Tue, 10 Dec 2002 14:11:13 +0530 Received: from scicmp.com (kanchenjunga [10.140.13.178]) by mx1.scicmp.com (8.9.3/8.8.7) with ESMTP id OAA28442; Tue, 10 Dec 2002 14:17:52 +0530 Message-ID: <3DF5A949.82BBFD7@scicmp.com> From: Sudipta Ghosh Organization: Scicom Infotech Pvt. Ltd. (Scicom) X-Mailer: Mozilla 4.79 [en] (Windows NT 5.0; U) X-Accept-Language: en,pdf MIME-Version: 1.0 To: Jonathan Rosenberg , sipforum , simple Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Subject: [Simple] SUBSCRIBE Sender: simple-admin@mailman.dynamicsoft.com Errors-To: simple-admin@mailman.dynamicsoft.com X-BeenThere: simple@mailman.dynamicsoft.com X-Mailman-Version: 2.0 Precedence: bulk List-Help: List-Post: List-Subscribe: , List-Id: SIP for Presence List-Unsubscribe: , List-Archive: Date: Tue, 10 Dec 2002 14:13:53 +0530 Content-Transfer-Encoding: 7bit Hi, I have a query. Suppose UAC AA is sending a SUBSCRIBE request for some event to another UAC BB via proxy server. At that BB was not online( I mean no yet registered ) so proxy server sent the 20o OK resonse to AA. After some time, when BB registered, I have noticed that proxy server is sending the SUBSCRIBE request, that AA has sent before. No everythinh is OK. AA gets event notification from BB. Now BB goes offline and close the dialog with AA for event for some time and then again registered. My query is how AA will again subscribe for event notification since AA does not have no info if BB is registerd or not.. Or proxy server will send SUBSCRIBE request? Where I will get documentation about this. sudipta -- *********************************************** System Executive Scicom Infotech Pvt. Ltd. (Scicom) A - 67, Sector - 57 Noida - 201 301 UP ********************************************** _______________________________________________ simple mailing list simple@mailman.dynamicsoft.com http://mailman.dynamicsoft.com/mailman/listinfo/simple From simple-admin@mailman.dynamicsoft.com Tue Dec 10 14:28:14 2002 Received: from mail1.dynamicsoft.com (mail1.dynamicsoft.com [63.113.40.10]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA18386 for ; Tue, 10 Dec 2002 14:28:14 -0500 (EST) Received: from mailman.dynamicsoft.com ([192.168.4.50]) by mail1.dynamicsoft.com (8.12.0.Beta7/8.12.0.Beta7) with ESMTP id gBAJT1Rh006851; Tue, 10 Dec 2002 14:29:01 -0500 (EST) Received: from mailman.dynamicsoft.com (localhost [127.0.0.1]) by mailman.dynamicsoft.com (8.9.3+Sun/8.9.3) with ESMTP id OAA06563; Tue, 10 Dec 2002 14:30:07 -0500 (EST) Received: from dyn-tx-arch-crash.dfw.dynamicsoft.com (dyn-tx-arch-crash.dfw.dynamicsoft.com [63.110.3.64]) by mailman.dynamicsoft.com (8.9.3+Sun/8.9.3) with ESMTP id OAA06550 for ; Tue, 10 Dec 2002 14:29:11 -0500 (EST) Received: from RjS.localdomain (localhost.localdomain [127.0.0.1]) by dyn-tx-arch-crash.dfw.dynamicsoft.com (8.11.6/8.11.6) with ESMTP id gBAJTCI23113 for ; Tue, 10 Dec 2002 13:29:12 -0600 From: Robert Sparks To: simple@mailman.dynamicsoft.com Content-Type: text/plain Content-Transfer-Encoding: 7bit X-Mailer: Ximian Evolution 1.0.8 (1.0.8-10) Message-Id: <1039548455.944.47.camel@RjS.localdomain> Mime-Version: 1.0 Subject: [Simple] Reminder: SIPit 12 Registration Sender: simple-admin@mailman.dynamicsoft.com Errors-To: simple-admin@mailman.dynamicsoft.com X-BeenThere: simple@mailman.dynamicsoft.com X-Mailman-Version: 2.0 Precedence: bulk List-Help: List-Post: List-Subscribe: , List-Id: SIP for Presence List-Unsubscribe: , List-Archive: Date: 10 Dec 2002 13:27:35 -0600 Content-Transfer-Encoding: 7bit The 12th SIPit will be hosted by Hotsip in Stockholm February 24-28, 2003. Please see http://www.hotsip.com/sipit12/ for details and registration. Registration closes January 20. RjS _______________________________________________ simple mailing list simple@mailman.dynamicsoft.com http://mailman.dynamicsoft.com/mailman/listinfo/simple From simple-admin@mailman.dynamicsoft.com Tue Dec 10 17:38:21 2002 Received: from mail1.dynamicsoft.com (mail1.dynamicsoft.com [63.113.40.10]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA23382 for ; Tue, 10 Dec 2002 17:38:21 -0500 (EST) Received: from mailman.dynamicsoft.com ([192.168.4.50]) by mail1.dynamicsoft.com (8.12.0.Beta7/8.12.0.Beta7) with ESMTP id gBAMd4Rh007611; Tue, 10 Dec 2002 17:39:04 -0500 (EST) Received: from mailman.dynamicsoft.com (localhost [127.0.0.1]) by mailman.dynamicsoft.com (8.9.3+Sun/8.9.3) with ESMTP id RAA07186; Tue, 10 Dec 2002 17:40:09 -0500 (EST) Received: from mail3.dynamicsoft.com (mail3.dynamicsoft.com [63.113.44.69]) by mailman.dynamicsoft.com (8.9.3+Sun/8.9.3) with ESMTP id RAA07173 for ; Tue, 10 Dec 2002 17:39:46 -0500 (EST) Received: from dynamicsoft.com ([63.113.46.78]) by mail3.dynamicsoft.com (8.12.1/8.12.1) with ESMTP id gBAMdlYH015072; Tue, 10 Dec 2002 17:39:50 -0500 (EST) Message-ID: <3DF66D2F.9030106@dynamicsoft.com> From: Jonathan Rosenberg Organization: dynamicsoft User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.1) Gecko/20020826 X-Accept-Language: en-us, en MIME-Version: 1.0 To: Sudipta Ghosh CC: sipforum , simple Subject: Re: [Simple] SUBSCRIBE References: <3DF5A949.82BBFD7@scicmp.com> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Sender: simple-admin@mailman.dynamicsoft.com Errors-To: simple-admin@mailman.dynamicsoft.com X-BeenThere: simple@mailman.dynamicsoft.com X-Mailman-Version: 2.0 Precedence: bulk List-Help: List-Post: List-Subscribe: , List-Id: SIP for Presence List-Unsubscribe: , List-Archive: Date: Tue, 10 Dec 2002 17:39:43 -0500 Content-Transfer-Encoding: 7bit What you are talking about here is subscription migration. It is described in some detail in RFC 3265, section 3.3.5. Generally, the UA lets the subscriber know that it has gone away by generating a NOTIFY with a Subscription-State header with a reason clause of deactivated. -Jonathan R. Sudipta Ghosh wrote: > Hi, > I have a query. > Suppose UAC AA is sending a SUBSCRIBE request for some event to another > UAC BB via proxy server. > At that BB was not online( I mean no yet registered ) so proxy server > sent the 20o OK resonse to AA. > > After some time, when BB registered, I have noticed that proxy server is > sending the SUBSCRIBE request, that AA has sent before. > No everythinh is OK. AA gets event notification from BB. > > Now BB goes offline and close the dialog with AA for event for some time > and then again registered. > My query is how AA will again subscribe for event notification since AA > does not have no info if BB is registerd or not.. > Or proxy server will send SUBSCRIBE request? > > Where I will get documentation about this. > > sudipta > > -- > *********************************************** > System Executive > Scicom Infotech Pvt. Ltd. (Scicom) > A - 67, Sector - 57 > Noida - 201 301 > UP > ********************************************** > > > _______________________________________________ > simple mailing list > simple@mailman.dynamicsoft.com > http://mailman.dynamicsoft.com/mailman/listinfo/simple > -- Jonathan D. Rosenberg, Ph.D. 72 Eagle Rock Ave. Chief Scientist First Floor dynamicsoft East Hanover, NJ 07936 jdrosen@dynamicsoft.com FAX: (973) 952-5050 http://www.jdrosen.net PHONE: (973) 952-5000 http://www.dynamicsoft.com _______________________________________________ simple mailing list simple@mailman.dynamicsoft.com http://mailman.dynamicsoft.com/mailman/listinfo/simple From simple-admin@mailman.dynamicsoft.com Wed Dec 11 09:39:14 2002 Received: from mail1.dynamicsoft.com (mail1.dynamicsoft.com [63.113.40.10]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA07000 for ; Wed, 11 Dec 2002 09:39:14 -0500 (EST) Received: from mailman.dynamicsoft.com ([192.168.4.50]) by mail1.dynamicsoft.com (8.12.0.Beta7/8.12.0.Beta7) with ESMTP id gBBEdvRh009757; Wed, 11 Dec 2002 09:39:57 -0500 (EST) Received: from mailman.dynamicsoft.com (localhost [127.0.0.1]) by mailman.dynamicsoft.com (8.9.3+Sun/8.9.3) with ESMTP id JAA09911; Wed, 11 Dec 2002 09:41:04 -0500 (EST) Received: from himalaya.scicmp.com ([203.200.79.36]) by mailman.dynamicsoft.com (8.9.3+Sun/8.9.3) with SMTP id JAA09900 for ; Wed, 11 Dec 2002 09:40:44 -0500 (EST) Received: from mx1.scicmp.com ([10.130.0.5]) by himalaya.scicmp.com (NAVGW 2.5.2.12) with SMTP id M2002121120110331497 ; Wed, 11 Dec 2002 20:11:03 +0530 Received: from scicmp.com (kanchenjunga [10.140.13.178]) by mx1.scicmp.com (8.9.3/8.8.7) with ESMTP id UAA24891; Wed, 11 Dec 2002 20:17:43 +0530 Message-ID: <3DF74F24.CA814E66@scicmp.com> From: Sudipta Ghosh Organization: Scicom Infotech Pvt. Ltd. (Scicom) X-Mailer: Mozilla 4.79 [en] (Windows NT 5.0; U) X-Accept-Language: en,pdf MIME-Version: 1.0 To: Jonathan Rosenberg , simple , sipforum Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Subject: [Simple] SIP servlet Sender: simple-admin@mailman.dynamicsoft.com Errors-To: simple-admin@mailman.dynamicsoft.com X-BeenThere: simple@mailman.dynamicsoft.com X-Mailman-Version: 2.0 Precedence: bulk List-Help: List-Post: List-Subscribe: , List-Id: SIP for Presence List-Unsubscribe: , List-Archive: Date: Wed, 11 Dec 2002 20:13:48 +0530 Content-Transfer-Encoding: 7bit Hi, I have some queries. where the sip servlet fits? I mean actual usage. Where I will get enough info regarding this. sudipta -- *********************************************** System Executive Scicom Infotech Pvt. Ltd. (Scicom) A - 67, Sector - 57 Noida - 201 301 UP ********************************************** _______________________________________________ simple mailing list simple@mailman.dynamicsoft.com http://mailman.dynamicsoft.com/mailman/listinfo/simple From simple-admin@mailman.dynamicsoft.com Wed Dec 11 09:53:03 2002 Received: from mail1.dynamicsoft.com (mail1.dynamicsoft.com [63.113.40.10]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA07582 for ; Wed, 11 Dec 2002 09:53:03 -0500 (EST) Received: from mailman.dynamicsoft.com ([192.168.4.50]) by mail1.dynamicsoft.com (8.12.0.Beta7/8.12.0.Beta7) with ESMTP id gBBErrRh009889; Wed, 11 Dec 2002 09:53:53 -0500 (EST) Received: from mailman.dynamicsoft.com (localhost [127.0.0.1]) by mailman.dynamicsoft.com (8.9.3+Sun/8.9.3) with ESMTP id JAA10008; Wed, 11 Dec 2002 09:55:03 -0500 (EST) Received: from mgw-x1.nokia.com (mgw-x1.nokia.com [131.228.20.21]) by mailman.dynamicsoft.com (8.9.3+Sun/8.9.3) with ESMTP id JAA09995 for ; Wed, 11 Dec 2002 09:54:04 -0500 (EST) From: aki.niemi@nokia.com Received: from esvir01nok.ntc.nokia.com (esvir01nokt.ntc.nokia.com [172.21.143.33]) by mgw-x1.nokia.com (Switch-2.2.1/Switch-2.2.0) with ESMTP id gBBErOG04172 for ; Wed, 11 Dec 2002 16:53:24 +0200 (EET) Received: from esebh002.NOE.Nokia.com (unverified) by esvir01nok.ntc.nokia.com (Content Technologies SMTPRS 4.2.5) with ESMTP id for ; Wed, 11 Dec 2002 16:54:04 +0200 Received: from esebe013.NOE.Nokia.com ([172.21.138.52]) by esebh002.NOE.Nokia.com with Microsoft SMTPSVC(5.0.2195.5329); Wed, 11 Dec 2002 16:54:04 +0200 X-MimeOLE: Produced By Microsoft Exchange V6.0.6249.0 content-class: urn:content-classes:message MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Message-ID: <98C7D2E5BCD2374C9AAE0BCD2E9C1DD901ADD134@esebe013.ntc.nokia.com> Thread-Topic: [Simple] who changes im: pres: to sip: Thread-Index: AcKQ3A7uYoFFjqAmR6WE/pGyJEF6jQAAWelwAAFppoAAANSlwAABKnNgAbOhXLA= To: X-OriginalArrivalTime: 11 Dec 2002 14:54:04.0651 (UTC) FILETIME=[2632A3B0:01C2A125] Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from quoted-printable to 8bit by mailman.dynamicsoft.com id JAA09995 Subject: [Simple] PUBLISH requirements Sender: simple-admin@mailman.dynamicsoft.com Errors-To: simple-admin@mailman.dynamicsoft.com X-BeenThere: simple@mailman.dynamicsoft.com X-Mailman-Version: 2.0 Precedence: bulk List-Help: List-Post: List-Subscribe: , List-Id: SIP for Presence List-Unsubscribe: , List-Archive: Date: Wed, 11 Dec 2002 16:54:04 +0200 Content-Transfer-Encoding: 8bit Hi All, The discussion in the SIMPLE session in Atlanta lead us towards another round of PUBLISH requirements. I think it would be good to look at some requirements that might be arising from the fact that the dynamics of publishing are distinctly different from the dynamics of notification. In presence notification, there is a single source, and multiple watchers representing a number of sinks. This of course is reflected in the PIDF format for presence documents, which states that each document contains complete state of the presentity, and tuples have unique IDs within that presence document, but carry no semantic value beyond that. But in presence publishing, there are multiple sources for presence information, represented by the PUAs, and only a single sink, represented by the composer. In order for the composer to make a coherent, single presence document out of the information coming from many sources, the composer should be able to identify the published information uniquely across all of the PUAs of a presentity. For example, if we say that a tuple is the base data unit of published presence information, then a specific tuple has to have a common ID across all PUAs of a presentity. In other words, the tuple-id needs to have semantics associated with it. This way the composer can merge two "im-inbox" publications into one single presence document tuple. This seems like an additional requirement for PIDF when it is used in publishing presence state. In addition to this, I think there may also be other requirements there related to expiration of state, and the fact that not all presence information is wrapped into a element. E.g., the presentity level element is not dependent of any tuples. How does one only publish a ? Or remove it? Thoughts? Cheers, Aki _______________________________________________ simple mailing list simple@mailman.dynamicsoft.com http://mailman.dynamicsoft.com/mailman/listinfo/simple From simple-admin@mailman.dynamicsoft.com Wed Dec 11 10:07:02 2002 Received: from mail1.dynamicsoft.com (mail1.dynamicsoft.com [63.113.40.10]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA08172 for ; Wed, 11 Dec 2002 10:07:01 -0500 (EST) Received: from mailman.dynamicsoft.com ([192.168.4.50]) by mail1.dynamicsoft.com (8.12.0.Beta7/8.12.0.Beta7) with ESMTP id gBBExqRh009978; Wed, 11 Dec 2002 09:59:52 -0500 (EST) Received: from mailman.dynamicsoft.com (localhost [127.0.0.1]) by mailman.dynamicsoft.com (8.9.3+Sun/8.9.3) with ESMTP id KAA10067; Wed, 11 Dec 2002 10:01:03 -0500 (EST) Received: from mgw-x4.nokia.com (mgw-x4.nokia.com [131.228.20.27]) by mailman.dynamicsoft.com (8.9.3+Sun/8.9.3) with ESMTP id KAA10056 for ; Wed, 11 Dec 2002 10:00:18 -0500 (EST) From: hisham.khartabil@nokia.com Received: from esvir04nok.ntc.nokia.com (esvir04nokt.ntc.nokia.com [172.21.143.36]) by mgw-x4.nokia.com (Switch-2.2.1/Switch-2.2.0) with ESMTP id gBBF1dW02964 for ; Wed, 11 Dec 2002 17:01:39 +0200 (EET) Received: from esebh003.NOE.Nokia.com (unverified) by esvir04nok.ntc.nokia.com (Content Technologies SMTPRS 4.2.5) with ESMTP id for ; Wed, 11 Dec 2002 17:00:16 +0200 Received: from esebh005.NOE.Nokia.com ([172.21.138.86]) by esebh003.NOE.Nokia.com with Microsoft SMTPSVC(5.0.2195.5329); Wed, 11 Dec 2002 17:00:15 +0200 Received: from esebe019.NOE.Nokia.com ([172.21.138.58]) by esebh005.NOE.Nokia.com with Microsoft SMTPSVC(5.0.2195.5329); Wed, 11 Dec 2002 17:00:14 +0200 X-MimeOLE: Produced By Microsoft Exchange V6.0.6249.0 content-class: urn:content-classes:message MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Message-ID: <2038BCC78B1AD641891A0D1AE133DBB7FE707D@esebe019.ntc.nokia.com> Thread-Topic: SUBSCRIBE with Accept-header for presence package (or any package) Thread-Index: AcKhJfz1HaPGRErwTEuZJ+kiTX/mFg== To: X-OriginalArrivalTime: 11 Dec 2002 15:00:14.0888 (UTC) FILETIME=[02E05280:01C2A126] Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from quoted-printable to 8bit by mailman.dynamicsoft.com id KAA10056 Subject: [Simple] SUBSCRIBE with Accept-header for presence package (or any package) Sender: simple-admin@mailman.dynamicsoft.com Errors-To: simple-admin@mailman.dynamicsoft.com X-BeenThere: simple@mailman.dynamicsoft.com X-Mailman-Version: 2.0 Precedence: bulk List-Help: List-Post: List-Subscribe: , List-Id: SIP for Presence List-Unsubscribe: , List-Archive: Date: Wed, 11 Dec 2002 17:00:06 +0200 Content-Transfer-Encoding: 8bit presence-09 says: "If the (accept) header field is present, it MUST include "application/cpim-pidf+xml", and MAY include any other types capable of representing user presence." But it also says: "All subscribers MUST support the "application/cpim-pidf+xml" presence data format described in [6]" But it doesn't say all notifiers must support "application/cpim-pidf+xml" "As described in RFC 3265 [2], the NOTIFY message will contain bodies that describe the state of the subscribed resource. This body is in a format listed in the Accept header field of the SUBSCRIBE, or a package-specific default if the Accept header field was omitted from the SUBSCRIBE." So, you would expect the Presence Server to reject the SUBSCRIBE if Accept header was present and did not include "application/cpim-pidf+xml", but no where in the document this is written. /Hisham _______________________________________________ simple mailing list simple@mailman.dynamicsoft.com http://mailman.dynamicsoft.com/mailman/listinfo/simple From simple-admin@mailman.dynamicsoft.com Wed Dec 11 17:24:10 2002 Received: from mail1.dynamicsoft.com (mail1.dynamicsoft.com [63.113.40.10]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA23521 for ; Wed, 11 Dec 2002 17:24:08 -0500 (EST) Received: from mailman.dynamicsoft.com ([192.168.4.50]) by mail1.dynamicsoft.com (8.12.0.Beta7/8.12.0.Beta7) with ESMTP id gBBME1Rh011701; Wed, 11 Dec 2002 17:14:02 -0500 (EST) Received: from mailman.dynamicsoft.com (localhost [127.0.0.1]) by mailman.dynamicsoft.com (8.9.3+Sun/8.9.3) with ESMTP id RAA11366; Wed, 11 Dec 2002 17:15:06 -0500 (EST) Received: from mail3.dynamicsoft.com (mail3.dynamicsoft.com [63.113.44.69]) by mailman.dynamicsoft.com (8.9.3+Sun/8.9.3) with ESMTP id RAA11353 for ; Wed, 11 Dec 2002 17:14:47 -0500 (EST) Received: from dynamicsoft.com ([63.113.47.242]) by mail3.dynamicsoft.com (8.12.1/8.12.1) with ESMTP id gBBMEoYH015640; Wed, 11 Dec 2002 17:14:50 -0500 (EST) Message-ID: <3DF7B8D7.6040404@dynamicsoft.com> From: Jonathan Rosenberg Organization: dynamicsoft User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.1) Gecko/20020826 X-Accept-Language: en-us, en MIME-Version: 1.0 To: hisham.khartabil@nokia.com CC: simple@mailman.dynamicsoft.com Subject: Re: [Simple] SUBSCRIBE with Accept-header for presence package (or any package) References: <2038BCC78B1AD641891A0D1AE133DBB7FE707D@esebe019.ntc.nokia.com> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Sender: simple-admin@mailman.dynamicsoft.com Errors-To: simple-admin@mailman.dynamicsoft.com X-BeenThere: simple@mailman.dynamicsoft.com X-Mailman-Version: 2.0 Precedence: bulk List-Help: List-Post: List-Subscribe: , List-Id: SIP for Presence List-Unsubscribe: , List-Archive: Date: Wed, 11 Dec 2002 17:14:47 -0500 Content-Transfer-Encoding: 7bit hisham.khartabil@nokia.com wrote: > presence-09 says: > > "If the (accept) header field is present, it MUST include > "application/cpim-pidf+xml", and MAY include any other types capable > of representing user presence." > > But it also says: > > "All subscribers MUST support the "application/cpim-pidf+xml" > presence data format described in [6]" > > But it doesn't say all notifiers must support > "application/cpim-pidf+xml" Yeah, you are right. Thats a bug probably. > > "As described in RFC 3265 [2], the NOTIFY message will contain bodies > that describe the state of the subscribed resource. This body is in > a format listed in the Accept header field of the SUBSCRIBE, or a > package-specific default if the Accept header field was omitted from > the SUBSCRIBE." > > So, you would expect the Presence Server to reject the SUBSCRIBE if > Accept header was present and did not include > "application/cpim-pidf+xml", but no where in the document this is > written. OK, we will get this fixed. Thanks, Jonathan R. -- Jonathan D. Rosenberg, Ph.D. 72 Eagle Rock Ave. Chief Scientist First Floor dynamicsoft East Hanover, NJ 07936 jdrosen@dynamicsoft.com FAX: (973) 952-5050 http://www.jdrosen.net PHONE: (973) 952-5000 http://www.dynamicsoft.com _______________________________________________ simple mailing list simple@mailman.dynamicsoft.com http://mailman.dynamicsoft.com/mailman/listinfo/simple From mailnull@www1.ietf.org Thu Dec 12 09:53:34 2002 Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA25809 for ; Thu, 12 Dec 2002 09:53:33 -0500 (EST) Received: (from mailnull@localhost) by www1.ietf.org (8.11.6/8.11.6) id gBCEu2U24066 for simple-archive@odin.ietf.org; Thu, 12 Dec 2002 09:56:02 -0500 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gBCEu2v24063 for ; Thu, 12 Dec 2002 09:56:02 -0500 Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA25799 for ; Thu, 12 Dec 2002 09:53:03 -0500 (EST) Received: from www1.ietf.org (localhost.localdomain [127.0.0.1]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gBCEu1v24058 for ; Thu, 12 Dec 2002 09:56:01 -0500 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gBCEtPv24042 for ; Thu, 12 Dec 2002 09:55:25 -0500 Received: from dyn-tx-arch-crash.dfw.dynamicsoft.com (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA25755 for ; Thu, 12 Dec 2002 09:52:26 -0500 (EST) Received: from RjS.localdomain (localhost.localdomain [127.0.0.1]) by dyn-tx-arch-crash.dfw.dynamicsoft.com (8.11.6/8.11.6) with ESMTP id gBCEtLI26958 for ; Thu, 12 Dec 2002 08:55:21 -0600 From: Robert Sparks To: simple@ietf.org Content-Type: text/plain Content-Transfer-Encoding: 7bit X-Mailer: Ximian Evolution 1.0.8 (1.0.8-10) Message-Id: <1039704813.958.3.camel@RjS.localdomain> Mime-Version: 1.0 Content-Transfer-Encoding: 7bit Subject: [Simple] administrative test Sender: simple-admin@ietf.org Errors-To: simple-admin@ietf.org X-BeenThere: simple@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: SIP for Instant Messaging and Presence Leveraging Extensions List-Post: List-Help: List-Subscribe: , List-Archive: Date: 12 Dec 2002 08:53:33 -0600 Content-Transfer-Encoding: 7bit Content-Transfer-Encoding: 7bit please ignore _______________________________________________ Simple mailing list Simple@ietf.org https://www1.ietf.org/mailman/listinfo/simple From simple-admin@mailman.dynamicsoft.com Fri Dec 13 00:35:06 2002 Received: from mail1.dynamicsoft.com (mail1.dynamicsoft.com [63.113.40.10]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id AAA04281 for ; Fri, 13 Dec 2002 00:34:51 -0500 (EST) Received: from mailman.dynamicsoft.com ([192.168.4.50]) by mail1.dynamicsoft.com (8.12.0.Beta7/8.12.0.Beta7) with ESMTP id gBD5Z1Rh017013; Fri, 13 Dec 2002 00:35:01 -0500 (EST) Received: from mailman.dynamicsoft.com (localhost [127.0.0.1]) by mailman.dynamicsoft.com (8.9.3+Sun/8.9.3) with ESMTP id AAA16977; Fri, 13 Dec 2002 00:36:06 -0500 (EST) Received: from mail3.dynamicsoft.com (mail3.dynamicsoft.com [63.113.44.69]) by mailman.dynamicsoft.com (8.9.3+Sun/8.9.3) with ESMTP id AAA16966 for ; Fri, 13 Dec 2002 00:35:57 -0500 (EST) Received: from dynamicsoft.com ([63.113.46.71]) by mail3.dynamicsoft.com (8.12.1/8.12.1) with ESMTP id gBD5ZxYH016599; Fri, 13 Dec 2002 00:35:59 -0500 (EST) Message-ID: <3DF971BC.1090107@dynamicsoft.com> From: Jonathan Rosenberg Organization: dynamicsoft User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.1) Gecko/20020826 X-Accept-Language: en-us, en MIME-Version: 1.0 To: aki.niemi@nokia.com CC: simple@mailman.dynamicsoft.com Subject: Re: [Simple] PUBLISH requirements References: <98C7D2E5BCD2374C9AAE0BCD2E9C1DD901ADD134@esebe013.ntc.nokia.com> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Sender: simple-admin@mailman.dynamicsoft.com Errors-To: simple-admin@mailman.dynamicsoft.com X-BeenThere: simple@mailman.dynamicsoft.com X-Mailman-Version: 2.0 Precedence: bulk List-Help: List-Post: List-Subscribe: , List-Id: SIP for Presence List-Unsubscribe: , List-Archive: Date: Fri, 13 Dec 2002 00:35:56 -0500 Content-Transfer-Encoding: 7bit aki.niemi@nokia.com wrote: > The discussion in the SIMPLE session in Atlanta lead us towards > another round of PUBLISH requirements. I think it would be good to > look at some requirements that might be arising from the fact that > the dynamics of publishing are distinctly different from the dynamics > of notification. Yes, I agree. Makes you glad we didn't go for NOTIFY as the publication mechanism... In order for the composer to make a > coherent, single presence document out of the information coming from > many sources, the composer should be able to identify the published > information uniquely across all of the PUAs of a presentity. The information is needed by others too. A presentity might want to setup a policy that says "only Joe and Bob can see my cell phone". That requires some unique way for the composer to identify which tuple is the cell phone. > > For example, if we say that a tuple is the base data unit of > published presence information, then a specific tuple has to have a > common ID across all PUAs of a presentity. In other words, the > tuple-id needs to have semantics associated with it. This way the > composer can merge two "im-inbox" publications into one single > presence document tuple. This seems like an additional requirement > for PIDF when it is used in publishing presence state. I think this is a slightly different issue than above. One requirement is just identification of the tuples whose scope is broader than the id attribute. What you are suggesting here, I think, is almost to define different classes of tuples. THis way, if I have two PCs, each of which has an "im-inbox", the composer could know to combine (or treat in the appropriate manner) those two tuples. That seems more of a slippery slope. > > In addition to this, I think there may also be other requirements > there related to expiration of state, and the fact that not all > presence information is wrapped into a element. E.g., the > presentity level element is not dependent of any tuples. How > does one only publish a ? Or remove it? Well, PIDF is going to change to allow a document with just a note. I raised this issue in IMPP and folks were ok with the change. Now, to remove a note, you'd presumably publish an empty document. That is, the assumption is that, as far as each publication instance is concerned, each publication represents the complete presence state from that instance. -Jonathan R. -- Jonathan D. Rosenberg, Ph.D. 72 Eagle Rock Ave. Chief Scientist First Floor dynamicsoft East Hanover, NJ 07936 jdrosen@dynamicsoft.com FAX: (973) 952-5050 http://www.jdrosen.net PHONE: (973) 952-5000 http://www.dynamicsoft.com _______________________________________________ simple mailing list simple@mailman.dynamicsoft.com http://mailman.dynamicsoft.com/mailman/listinfo/simple From simple-admin@mailman.dynamicsoft.com Mon Dec 16 17:14:34 2002 Received: from mail1.dynamicsoft.com (mail1.dynamicsoft.com [63.113.40.10]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA19986 for ; Mon, 16 Dec 2002 17:14:34 -0500 (EST) Received: from mailman.dynamicsoft.com ([192.168.4.50]) by mail1.dynamicsoft.com (8.12.0.Beta7/8.12.0.Beta7) with ESMTP id gBGMFHKW002973; Mon, 16 Dec 2002 17:15:17 -0500 (EST) Received: from mailman.dynamicsoft.com (localhost [127.0.0.1]) by mailman.dynamicsoft.com (8.9.3+Sun/8.9.3) with ESMTP id RAA02391; Mon, 16 Dec 2002 17:16:16 -0500 (EST) Received: from oe-im2.bizmailsrvcs.net (oe-im2pub.managedmail.com [206.46.164.53]) by mailman.dynamicsoft.com (8.9.3+Sun/8.9.3) with ESMTP id RAA02380 for ; Mon, 16 Dec 2002 17:15:37 -0500 (EST) Received: from oe-ismta2.bizmailsrvcs.net ([206.46.164.27]) by oe-im2.bizmailsrvcs.net (InterMail vM.5.01.05.12 201-253-122-126-112-20020820) with ESMTP id <20021216221537.DKPG2778.oe-im2.bizmailsrvcs.net@oe-ismta2.bizmailsrvcs.net>; Mon, 16 Dec 2002 16:15:37 -0600 Received: from RoselinskyM ([64.14.194.185]) by oe-ismta2.bizmailsrvcs.net (InterMail vM.5.01.05.20 201-253-122-126-120-20021101) with SMTP id <20021216221532.HYGG3996.oe-ismta2.bizmailsrvcs.net@RoselinskyM>; Mon, 16 Dec 2002 16:15:32 -0600 From: "Milt Roselinsky" To: , Subject: RE: [Simple] 3GPP Messaging requirements Message-ID: MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 8bit 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.1106 Importance: Normal In-reply-to: <98C7D2E5BCD2374C9AAE0BCD2E9C1DD901945054@esebe013.ntc.nokia.com> Sender: simple-admin@mailman.dynamicsoft.com Errors-To: simple-admin@mailman.dynamicsoft.com X-BeenThere: simple@mailman.dynamicsoft.com X-Mailman-Version: 2.0 Precedence: bulk List-Help: List-Post: List-Subscribe: , List-Id: SIP for Presence List-Unsubscribe: , List-Archive: Date: Mon, 16 Dec 2002 14:15:31 -0800 Content-Transfer-Encoding: 8bit Aki, Thank you for putting together this summary of messaging requirements for 3GPP. Sorry I didn't reply earlier but I was informed of this activity very recently. I participated in the 3GPP SA1 messaging sub-working group that wrote the stage 1 requirements for 3GPP messaging. I have a few suggestions that would make your ID more complete. First, I suggest changing the word "wireless" in the title to "3GPP" to more clearly reflect the contents of the ID. Section 3.2 Message Content Requirements Regarding the OPEN ISSUE on content sequencing. The sequencing of media in 3GPP messaging is currently handled by a subset of the Synchronized Multimedia Integration Language (SMIL). As mentioned in Section 2, terminals are simple devices and there is often a problem with terminals trying to exchange multimedia messages when the media support in thesender and recipient don’t match up. There is a requirement that says: The recipient's network MUST be able to take into account the recipient's terminal capabilities and translate message content into a form that can be used on the recipient’s terminal. NOTE: Although this isn’t a protocol issue, there are a minimum set of media formats that MUST be supported in all 3GPP messaging clients, defined in 3GPP TS 26.140 and 3GPP TS 26.234. Section 3.4 Message Delivery and Handling Requirements There is an additional 3GPP requirement that says: It MUST be possible for the UA be able to store immediate messages in a persistent network-based message store and then to subsequently retrieve, list, delete and forward immediate messages. The statement of requirements for message filtering in section 3.4 is incomplete. Some filtering criteria from the 3GPP requirements were left off of the list. The original wording of 3.4 says: It MUST be possible to divert or block instant messages as part of a user configurable option. Such mechanisms MUST support instant message diversion based on sender address, message size, message priority, message subject, message class and message content type. The mechanism MAY support instant message diversion based on other message properties. The missing message filter criteria are message type and recipient’s presence status. There are also a number of required actions resulting from a filter match beyond divert and block. These are: 1) Store the message content and notify recipient. 2) Store the message content for a specific time or until the recipient requests delivery. 3) Store and push the message content to recipient when available. In the Normative References section, in addition to 3GPP TR 22.940 the ID should also refer to 3GPP TS 23.340, "IMS Messaging Stage 1". Best regards, Milt Roselinsky Openwave Systems milt.roselinsky@openwave.com +1.805.884.6207 > -----Original Message----- > From: simple-admin@mailman.dynamicsoft.com > [mailto:simple-admin@mailman.dynamicsoft.com]On Behalf Of > aki.niemi@nokia.com > Sent: Wednesday, October 30, 2002 2:37 AM > To: simple@mailman.dynamicsoft.com > Subject: [Simple] 3GPP Messaging requirements > > > Hi All, > > Like promised in Yokohama, there is now a document available > describing the 3GPP requirements to Instant Messaging. It lists > requirements for both pager mode and session mode IM. Here's a > link for your convenience: > > http://www.ietf.org/internet-drafts/draft-niemi-simple-im-wireless -reqs-00.txt I'd especially like to draw your attention to the requirements for session mode IM, as well as the requirements for data manipulation. Note also, that when 3GPP talks about session based messaging, there is a strong flavor of multiparty sessions to it. The conferencing aspects, and the chat-room type aspects of this document should be considered already in the current message session work. Cheers, Aki _______________________________________________ simple mailing list simple@mailman.dynamicsoft.com http://mailman.dynamicsoft.com/mailman/listinfo/simple _______________________________________________ simple mailing list simple@mailman.dynamicsoft.com http://mailman.dynamicsoft.com/mailman/listinfo/simple From simple-admin@mailman.dynamicsoft.com Tue Dec 17 01:42:56 2002 Received: from mail1.dynamicsoft.com (mail1.dynamicsoft.com [63.113.40.10]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id BAA27706 for ; Tue, 17 Dec 2002 01:42:56 -0500 (EST) Received: from mailman.dynamicsoft.com ([192.168.4.50]) by mail1.dynamicsoft.com (8.12.0.Beta7/8.12.0.Beta7) with ESMTP id gBH6hqKW004022; Tue, 17 Dec 2002 01:43:53 -0500 (EST) Received: from mailman.dynamicsoft.com (localhost [127.0.0.1]) by mailman.dynamicsoft.com (8.9.3+Sun/8.9.3) with ESMTP id BAA03916; Tue, 17 Dec 2002 01:45:04 -0500 (EST) Received: from mail3.dynamicsoft.com (mail3.dynamicsoft.com [63.113.44.69]) by mailman.dynamicsoft.com (8.9.3+Sun/8.9.3) with ESMTP id BAA03903 for ; Tue, 17 Dec 2002 01:44:20 -0500 (EST) Received: from dynamicsoft.com ([63.113.46.70]) by mail3.dynamicsoft.com (8.12.1/8.12.1) with ESMTP id gBH6iMYH018522; Tue, 17 Dec 2002 01:44:22 -0500 (EST) Message-ID: <3DFEC7C3.8020807@dynamicsoft.com> From: Jonathan Rosenberg Organization: dynamicsoft User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.1) Gecko/20020826 X-Accept-Language: en-us, en MIME-Version: 1.0 To: Milt Roselinsky CC: aki.niemi@nokia.com, simple@mailman.dynamicsoft.com Subject: Re: [Simple] 3GPP Messaging requirements References: Content-Type: text/plain; charset=windows-1252; format=flowed Content-Transfer-Encoding: 8bit Sender: simple-admin@mailman.dynamicsoft.com Errors-To: simple-admin@mailman.dynamicsoft.com X-BeenThere: simple@mailman.dynamicsoft.com X-Mailman-Version: 2.0 Precedence: bulk List-Help: List-Post: List-Subscribe: , List-Id: SIP for Presence List-Unsubscribe: , List-Archive: Date: Tue, 17 Dec 2002 01:44:19 -0500 Content-Transfer-Encoding: 8bit This note is timely. I am about to submit an IM requirements I-D which incorporates some of the requirements from Aki's draft (those which we can't do and require SIP/SIMPLE work), in addition to some others that I believe we need to address. Comments inline. Milt Roselinsky wrote: > As mentioned in Section 2, terminals are simple devices and there is often a > problem with terminals trying to exchange multimedia messages when the > media support in thesender and recipient don’t match up. There is a > requirement that says: > The recipient's network MUST be able to take into account > the recipient's terminal capabilities and translate > message content into a form that can be used on the recipient’s terminal. Content transcoding has been an active area of debate for sipping recently. I think we concluded it was out of scope in sipping. I think its out of scope here too; those requirements need to go to opes. > The statement of requirements for message filtering in section 3.4 is > incomplete. Some filtering criteria from the 3GPP requirements were left > off of the list. > > The original wording of 3.4 says: > It MUST be possible to divert or block instant messages as part of a > user configurable option. Such mechanisms MUST support instant > message diversion based on sender address, message size, message > priority, message subject, message class and message content type. > The mechanism MAY support instant message diversion based on other > message properties. > > The missing message filter criteria are message type and recipient’s > presence status. What is message type? Thanks, Jonathan R. -- Jonathan D. Rosenberg, Ph.D. 72 Eagle Rock Ave. Chief Scientist First Floor dynamicsoft East Hanover, NJ 07936 jdrosen@dynamicsoft.com FAX: (973) 952-5050 http://www.jdrosen.net PHONE: (973) 952-5000 http://www.dynamicsoft.com _______________________________________________ simple mailing list simple@mailman.dynamicsoft.com http://mailman.dynamicsoft.com/mailman/listinfo/simple From simple-admin@mailman.dynamicsoft.com Tue Dec 17 02:07:00 2002 Received: from mail1.dynamicsoft.com (mail1.dynamicsoft.com [63.113.40.10]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id CAA07383 for ; Tue, 17 Dec 2002 02:06:59 -0500 (EST) Received: from mailman.dynamicsoft.com ([192.168.4.50]) by mail1.dynamicsoft.com (8.12.0.Beta7/8.12.0.Beta7) with ESMTP id gBH77nKW004128; Tue, 17 Dec 2002 02:07:49 -0500 (EST) Received: from mailman.dynamicsoft.com (localhost [127.0.0.1]) by mailman.dynamicsoft.com (8.9.3+Sun/8.9.3) with ESMTP id CAA04025; Tue, 17 Dec 2002 02:09:03 -0500 (EST) Received: from mail3.dynamicsoft.com (mail3.dynamicsoft.com [63.113.44.69]) by mailman.dynamicsoft.com (8.9.3+Sun/8.9.3) with ESMTP id CAA04014 for ; Tue, 17 Dec 2002 02:08:11 -0500 (EST) Received: from dynamicsoft.com ([63.113.46.70]) by mail3.dynamicsoft.com (8.12.1/8.12.1) with ESMTP id gBH78EYH018530 for ; Tue, 17 Dec 2002 02:08:14 -0500 (EST) Message-ID: <3DFECD5B.2010807@dynamicsoft.com> From: Jonathan Rosenberg Organization: dynamicsoft User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.1) Gecko/20020826 X-Accept-Language: en-us, en MIME-Version: 1.0 To: simple@mailman.dynamicsoft.com Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Subject: [Simple] new I-D on advanced IM requirements Sender: simple-admin@mailman.dynamicsoft.com Errors-To: simple-admin@mailman.dynamicsoft.com X-BeenThere: simple@mailman.dynamicsoft.com X-Mailman-Version: 2.0 Precedence: bulk List-Help: List-Post: List-Subscribe: , List-Id: SIP for Presence List-Unsubscribe: , List-Archive: Date: Tue, 17 Dec 2002 02:08:11 -0500 Content-Transfer-Encoding: 7bit Folks, One of the items on our charter is this: SEP 02 Submission of advanced messaging requirements draft to IESG for publication as Informational to date, we have not had even an I-D written to specifically address this item (clearly we are behind schedule). So, I have collected IM requirements from (1) Aki's 3gpp requirements draft, (2) the old SIMPLE components draft (http://www.jdrosen.net/papers/draft-rosenberg-simple-components-00.txt), gaps between SIMPLE and some other systems, such as wireless village. I've put those in a new I-D which I've just submitted. Until it appears, you can pick it up at: http://www.jdrosen.net/papers/draft-rosenberg-simple-components-00.txt http://www.jdrosen.net/papers/draft-rosenberg-simple-components-00.html There are definitely some controversial issues here. I listed a bunch of requirements I am not sure we should even try to meet. But, it is worth discussing. It is my hope that this document can serve as the basis for the charter item above, if there is consensus in the group to move forward with it. THanks, Jonathan R. -- Jonathan D. Rosenberg, Ph.D. 72 Eagle Rock Ave. Chief Scientist First Floor dynamicsoft East Hanover, NJ 07936 jdrosen@dynamicsoft.com FAX: (973) 952-5050 http://www.jdrosen.net PHONE: (973) 952-5000 http://www.dynamicsoft.com _______________________________________________ simple mailing list simple@mailman.dynamicsoft.com http://mailman.dynamicsoft.com/mailman/listinfo/simple From simple-admin@mailman.dynamicsoft.com Tue Dec 17 11:43:02 2002 Received: from mail1.dynamicsoft.com (mail1.dynamicsoft.com [63.113.40.10]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA17071 for ; Tue, 17 Dec 2002 11:42:56 -0500 (EST) Received: from mailman.dynamicsoft.com ([192.168.4.50]) by mail1.dynamicsoft.com (8.12.0.Beta7/8.12.0.Beta7) with ESMTP id gBHGhrKW005643; Tue, 17 Dec 2002 11:43:53 -0500 (EST) Received: from mailman.dynamicsoft.com (localhost [127.0.0.1]) by mailman.dynamicsoft.com (8.9.3+Sun/8.9.3) with ESMTP id LAA05715; Tue, 17 Dec 2002 11:45:05 -0500 (EST) Received: from oe-im2.bizmailsrvcs.net (oe-im2pub.managedmail.com [206.46.164.53]) by mailman.dynamicsoft.com (8.9.3+Sun/8.9.3) with ESMTP id LAA05702 for ; Tue, 17 Dec 2002 11:44:37 -0500 (EST) Received: from oe-ismta2.bizmailsrvcs.net ([206.46.164.27]) by oe-im2.bizmailsrvcs.net (InterMail vM.5.01.05.12 201-253-122-126-112-20020820) with ESMTP id <20021217164438.GYZL2778.oe-im2.bizmailsrvcs.net@oe-ismta2.bizmailsrvcs.net>; Tue, 17 Dec 2002 10:44:38 -0600 Received: from RoselinskyM ([206.35.147.89]) by oe-ismta2.bizmailsrvcs.net (InterMail vM.5.01.05.20 201-253-122-126-120-20021101) with SMTP id <20021217164438.LHFM3996.oe-ismta2.bizmailsrvcs.net@RoselinskyM>; Tue, 17 Dec 2002 10:44:38 -0600 From: "Milt Roselinsky" To: "Jonathan Rosenberg" Cc: , Subject: RE: [Simple] 3GPP Messaging requirements Message-ID: MIME-Version: 1.0 Content-Type: text/plain; charset="Windows-1252" Content-Transfer-Encoding: 8bit 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.1106 Importance: Normal In-reply-to: <3DFEC7C3.8020807@dynamicsoft.com> Sender: simple-admin@mailman.dynamicsoft.com Errors-To: simple-admin@mailman.dynamicsoft.com X-BeenThere: simple@mailman.dynamicsoft.com X-Mailman-Version: 2.0 Precedence: bulk List-Help: List-Post: List-Subscribe: , List-Id: SIP for Presence List-Unsubscribe: , List-Archive: Date: Tue, 17 Dec 2002 08:44:38 -0800 Content-Transfer-Encoding: 8bit > > > > The missing message filter criteria are message type and recipient’s > > presence status. > > What is message type? immediate or session based message > > Thanks, > Jonathan R. > > -- > Jonathan D. Rosenberg, Ph.D. 72 Eagle Rock Ave. > Chief Scientist First Floor > dynamicsoft East Hanover, NJ 07936 > jdrosen@dynamicsoft.com FAX: (973) 952-5050 > http://www.jdrosen.net PHONE: (973) 952-5000 > http://www.dynamicsoft.com > > _______________________________________________ > simple mailing list > simple@mailman.dynamicsoft.com > http://mailman.dynamicsoft.com/mailman/listinfo/simple _______________________________________________ simple mailing list simple@mailman.dynamicsoft.com http://mailman.dynamicsoft.com/mailman/listinfo/simple From simple-admin@mailman.dynamicsoft.com Tue Dec 17 11:48:46 2002 Received: from mail1.dynamicsoft.com (mail1.dynamicsoft.com [63.113.40.10]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA17219 for ; Tue, 17 Dec 2002 11:48:45 -0500 (EST) Received: from mailman.dynamicsoft.com ([192.168.4.50]) by mail1.dynamicsoft.com (8.12.0.Beta7/8.12.0.Beta7) with ESMTP id gBHGnmKW005739; Tue, 17 Dec 2002 11:49:48 -0500 (EST) Received: from mailman.dynamicsoft.com (localhost [127.0.0.1]) by mailman.dynamicsoft.com (8.9.3+Sun/8.9.3) with ESMTP id LAA05765; Tue, 17 Dec 2002 11:51:04 -0500 (EST) Received: from mail3.dynamicsoft.com (mail3.dynamicsoft.com [63.113.44.69]) by mailman.dynamicsoft.com (8.9.3+Sun/8.9.3) with ESMTP id LAA05750 for ; Tue, 17 Dec 2002 11:50:31 -0500 (EST) Received: from dynamicsoft.com ([63.113.46.95]) by mail3.dynamicsoft.com (8.12.1/8.12.1) with ESMTP id gBHGoYYH018770; Tue, 17 Dec 2002 11:50:34 -0500 (EST) Message-ID: <3DFF55D7.8060908@dynamicsoft.com> From: Jonathan Rosenberg Organization: dynamicsoft User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.1) Gecko/20020826 X-Accept-Language: en-us, en MIME-Version: 1.0 To: Milt Roselinsky CC: aki.niemi@nokia.com, simple@mailman.dynamicsoft.com Subject: Re: [Simple] 3GPP Messaging requirements References: Content-Type: text/plain; charset=windows-1252; format=flowed Content-Transfer-Encoding: 8bit Sender: simple-admin@mailman.dynamicsoft.com Errors-To: simple-admin@mailman.dynamicsoft.com X-BeenThere: simple@mailman.dynamicsoft.com X-Mailman-Version: 2.0 Precedence: bulk List-Help: List-Post: List-Subscribe: , List-Id: SIP for Presence List-Unsubscribe: , List-Archive: Date: Tue, 17 Dec 2002 11:50:31 -0500 Content-Transfer-Encoding: 8bit Milt Roselinsky wrote: >>>The missing message filter criteria are message type and recipient’s >>>presence status. >> >>What is message type? > > > immediate or session based message Just to be sure we are on the same page with terminology, "immediate" is page mode (i.e, RFC 3428, the MESSAGE method), and session-based are as per draft-campbell-simple-im-sessions? -Jonathan R. -- Jonathan D. Rosenberg, Ph.D. 72 Eagle Rock Ave. Chief Scientist First Floor dynamicsoft East Hanover, NJ 07936 jdrosen@dynamicsoft.com FAX: (973) 952-5050 http://www.jdrosen.net PHONE: (973) 952-5000 http://www.dynamicsoft.com _______________________________________________ simple mailing list simple@mailman.dynamicsoft.com http://mailman.dynamicsoft.com/mailman/listinfo/simple From simple-admin@mailman.dynamicsoft.com Tue Dec 17 12:18:47 2002 Received: from mail1.dynamicsoft.com (mail1.dynamicsoft.com [63.113.40.10]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA18016 for ; Tue, 17 Dec 2002 12:18:47 -0500 (EST) Received: from mailman.dynamicsoft.com ([192.168.4.50]) by mail1.dynamicsoft.com (8.12.0.Beta7/8.12.0.Beta7) with ESMTP id gBHHJmKW005944; Tue, 17 Dec 2002 12:19:48 -0500 (EST) Received: from mailman.dynamicsoft.com (localhost [127.0.0.1]) by mailman.dynamicsoft.com (8.9.3+Sun/8.9.3) with ESMTP id MAA05944; Tue, 17 Dec 2002 12:21:03 -0500 (EST) Received: from mail3.dynamicsoft.com (mail3.dynamicsoft.com [63.113.44.69]) by mailman.dynamicsoft.com (8.9.3+Sun/8.9.3) with ESMTP id MAA05933 for ; Tue, 17 Dec 2002 12:20:18 -0500 (EST) Received: from dynamicsoft.com ([63.113.46.95]) by mail3.dynamicsoft.com (8.12.1/8.12.1) with ESMTP id gBHHKKYH018787; Tue, 17 Dec 2002 12:20:21 -0500 (EST) Message-ID: <3DFF5CD1.90402@dynamicsoft.com> From: Jonathan Rosenberg Organization: dynamicsoft User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.1) Gecko/20020826 X-Accept-Language: en-us, en MIME-Version: 1.0 To: Brian Raymor , simple@mailman.dynamicsoft.com Subject: Re: [Simple] new I-D on advanced IM requirements References: <200212171715.gBHHFuq20136@nasnfs.Eng.Sun.COM> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Sender: simple-admin@mailman.dynamicsoft.com Errors-To: simple-admin@mailman.dynamicsoft.com X-BeenThere: simple@mailman.dynamicsoft.com X-Mailman-Version: 2.0 Precedence: bulk List-Help: List-Post: List-Subscribe: , List-Id: SIP for Presence List-Unsubscribe: , List-Archive: Date: Tue, 17 Dec 2002 12:20:17 -0500 Content-Transfer-Encoding: 7bit Oops, yes. Thanks for noting this. -Jonathan R. Brian Raymor wrote: > >>I've put those in a new I-D which I've just submitted. Until it appears, >>you can pick it up at: >> >>http://www.jdrosen.net/papers/draft-rosenberg-simple-components-00.txt >>http://www.jdrosen.net/papers/draft-rosenberg-simple-components-00.html > > > Did you mean: > > http://www.jdrosen.net/papers/draft-rosenberg-simple-messaging-requirements-00.h > tml > http://www.jdrosen.net/papers/draft-rosenberg-simple-messaging-requirements-00.t > xt > > -- Jonathan D. Rosenberg, Ph.D. 72 Eagle Rock Ave. Chief Scientist First Floor dynamicsoft East Hanover, NJ 07936 jdrosen@dynamicsoft.com FAX: (973) 952-5050 http://www.jdrosen.net PHONE: (973) 952-5000 http://www.dynamicsoft.com _______________________________________________ simple mailing list simple@mailman.dynamicsoft.com http://mailman.dynamicsoft.com/mailman/listinfo/simple From simple-admin@mailman.dynamicsoft.com Wed Dec 18 01:03:03 2002 Received: from mail1.dynamicsoft.com (mail1.dynamicsoft.com [63.113.40.10]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id BAA03521 for ; Wed, 18 Dec 2002 01:03:02 -0500 (EST) Received: from mailman.dynamicsoft.com ([192.168.4.50]) by mail1.dynamicsoft.com (8.12.0.Beta7/8.12.0.Beta7) with ESMTP id gBI63xKW008268; Wed, 18 Dec 2002 01:04:00 -0500 (EST) Received: from mailman.dynamicsoft.com (localhost [127.0.0.1]) by mailman.dynamicsoft.com (8.9.3+Sun/8.9.3) with ESMTP id BAA08192; Wed, 18 Dec 2002 01:05:06 -0500 (EST) Received: from hitpro.hitachi.co.jp (hitpro.hitachi.co.jp [133.145.224.7]) by mailman.dynamicsoft.com (8.9.3+Sun/8.9.3) with ESMTP id BAA08179 for ; Wed, 18 Dec 2002 01:04:11 -0500 (EST) Received: from mc1.mcg.hitachi.co.jp by hitpro.hitachi.co.jp (8.9.3/3.7W-hitpro) id PAA27187; Wed, 18 Dec 2002 15:04:09 +0900 (JST) Received: (from root@localhost) by mc1.mcg.hitachi.co.jp (8.11.6+Sun/8.11.6) id gBI647612686 for ; Wed, 18 Dec 2002 15:04:07 +0900 (JST) Received: from unknown [192.168.2.1] by mc1.mcg.hitachi.co.jp with SMTP id RAA12683 ; Wed, 18 Dec 2002 15:04:07 +0900 Received: from navsg1.hitachi.co.jp by navsg1.hitachi.co.jp (8.9.3/3.7W-navsg1) id PAA19440; Wed, 18 Dec 2002 15:04:07 +0900 (JST) Received: from hsdlgw92.sdl.hitachi.co.jp ([133.144.7.20]) by navsg1.hitachi.co.jp (NAVGW 2.5.2.17) with SMTP id M2002121815040601983 for ; Wed, 18 Dec 2002 15:04:07 +0900 Received: from vgate.sdl.hitachi.co.jp by hsdlgw92.sdl.hitachi.co.jp (8.9.3/3.7W01100113) id PAA10882; Wed, 18 Dec 2002 15:04:06 +0900 Received: from yokolab2.sdl.hitachi.co.jp ([133.144.101.10]) by vgate.sdl.hitachi.co.jp (NAVGW 2.5.1.16) with SMTP id M2002121815040717943 ; Wed, 18 Dec 2002 15:04:07 +0900 Received: from sdl.hitachi.co.jp ([158.213.146.124]) by yokolab2.sdl.hitachi.co.jp (8.9.3/3.7W02021014) with ESMTP id PAA14887; Wed, 18 Dec 2002 15:04:06 +0900 Message-ID: <3E000CBF.FF94D447@sdl.hitachi.co.jp> From: Kenta Shiga X-Mailer: Mozilla 4.78 [ja] (Windows NT 5.0; U) X-Accept-Language: ja MIME-Version: 1.0 To: Jonathan Rosenberg , Miyata , Fujiwara Keisei , Tanaka Tooru CC: Brian Raymor , simple@mailman.dynamicsoft.com Subject: Re: [Simple] new I-D on advanced IM requirements References: <200212171715.gBHHFuq20136@nasnfs.Eng.Sun.COM> <3DFF5CD1.90402@dynamicsoft.com> Content-Type: text/plain; charset=iso-2022-jp Content-Transfer-Encoding: 7bit Sender: simple-admin@mailman.dynamicsoft.com Errors-To: simple-admin@mailman.dynamicsoft.com X-BeenThere: simple@mailman.dynamicsoft.com X-Mailman-Version: 2.0 Precedence: bulk List-Help: List-Post: List-Subscribe: , List-Id: SIP for Presence List-Unsubscribe: , List-Archive: Date: Wed, 18 Dec 2002 14:50:55 +0900 Content-Transfer-Encoding: 7bit TO:($B5\ED(B)($BEDCf(B)($BF#86(B) $B;V2l$G$9!#(B Rosenberg$B$,%j%s%/$r4V0c$($?$i$7$$!#(B $B@5$7$/$O!$(B http://www.jdrosen.net/papers/draft-rosenberg-simple-messaging-requirements-00.html http://www.jdrosen.net/papers/draft-rosenberg-simple-messaging-requirements-00.txt $B$G$9!#(B Jonathan Rosenberg wrote: > Oops, yes. Thanks for noting this. > > -Jonathan R. > > Brian Raymor wrote: > > > >>I've put those in a new I-D which I've just submitted. Until it appears, > >>you can pick it up at: > >> > >>http://www.jdrosen.net/papers/draft-rosenberg-simple-components-00.txt > >>http://www.jdrosen.net/papers/draft-rosenberg-simple-components-00.html > > > > > > Did you mean: > > > > http://www.jdrosen.net/papers/draft-rosenberg-simple-messaging-requirements-00.h > > tml > > http://www.jdrosen.net/papers/draft-rosenberg-simple-messaging-requirements-00.t > > xt > > > > > > -- > Jonathan D. Rosenberg, Ph.D. 72 Eagle Rock Ave. > Chief Scientist First Floor > dynamicsoft East Hanover, NJ 07936 > jdrosen@dynamicsoft.com FAX: (973) 952-5050 > http://www.jdrosen.net PHONE: (973) 952-5000 > http://www.dynamicsoft.com > > _______________________________________________ > simple mailing list > simple@mailman.dynamicsoft.com > http://mailman.dynamicsoft.com/mailman/listinfo/simple -- Kenta Shiga, Researcher Systems Development Laboratory, Hitachi,Ltd. Tel: +81 45 860 3077 (ext.874-4435) Fax: +81 45 860 1675 (ext.874-4402) _______________________________________________ simple mailing list simple@mailman.dynamicsoft.com http://mailman.dynamicsoft.com/mailman/listinfo/simple From simple-admin@mailman.dynamicsoft.com Fri Dec 20 07:09:04 2002 Received: from mail1.dynamicsoft.com (mail1.dynamicsoft.com [63.113.40.10]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA22944 for ; Fri, 20 Dec 2002 07:09:04 -0500 (EST) Received: from mailman.dynamicsoft.com ([192.168.4.50]) by mail1.dynamicsoft.com (8.12.0.Beta7/8.12.0.Beta7) with ESMTP id gBKC9wKW017008; Fri, 20 Dec 2002 07:09:58 -0500 (EST) Received: from mailman.dynamicsoft.com (localhost [127.0.0.1]) by mailman.dynamicsoft.com (8.9.3+Sun/8.9.3) with ESMTP id HAA17621; Fri, 20 Dec 2002 07:11:06 -0500 (EST) Received: from ietf.org (odin.ietf.org [132.151.1.176]) by mailman.dynamicsoft.com (8.9.3+Sun/8.9.3) with ESMTP id HAA17610 for ; Fri, 20 Dec 2002 07:10:28 -0500 (EST) Received: from CNRI.Reston.VA.US (localhost [127.0.0.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA22618; Fri, 20 Dec 2002 07:07:28 -0500 (EST) Message-Id: <200212201207.HAA22618@ietf.org> Mime-Version: 1.0 Content-Type: Multipart/Mixed; Boundary="NextPart" To: IETF-Announce: ; CC: simple@mailman.dynamicsoft.com From: Internet-Drafts@ietf.org Reply-to: Internet-Drafts@ietf.org Subject: [Simple] I-D ACTION:draft-rosenberg-simple-messaging-requirements-00.txt Sender: simple-admin@mailman.dynamicsoft.com Errors-To: simple-admin@mailman.dynamicsoft.com X-BeenThere: simple@mailman.dynamicsoft.com X-Mailman-Version: 2.0 Precedence: bulk List-Help: List-Post: List-Subscribe: , List-Id: SIP for Presence List-Unsubscribe: , List-Archive: Date: Fri, 20 Dec 2002 07:07:27 -0500 --NextPart A New Internet-Draft is available from the on-line Internet-Drafts directories. Title : Advanced Instant Messaging Requirements for the Session Initiation Protocol (SIP) Author(s) : J. Rosenberg Filename : draft-rosenberg-simple-messaging-requirements-00.txt Pages : 18 Date : 2002-12-18 This specification defines a set of requirements for new capabilities for instant messaging and presence in SIP-based systems. A URL for this Internet-Draft is: http://www.ietf.org/internet-drafts/draft-rosenberg-simple-messaging-requirements-00.txt To remove yourself from the IETF Announcement list, send a message to ietf-announce-request with the word unsubscribe in the body of the message. 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-rosenberg-simple-messaging-requirements-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-rosenberg-simple-messaging-requirements-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. --NextPart Content-Type: Multipart/Alternative; Boundary="OtherAccess" --OtherAccess Content-Type: Message/External-body; access-type="mail-server"; server="mailserv@ietf.org" Content-Type: text/plain Content-ID: <2002-12-18131555.I-D@ietf.org> ENCODING mime FILE /internet-drafts/draft-rosenberg-simple-messaging-requirements-00.txt --OtherAccess Content-Type: Message/External-body; name="draft-rosenberg-simple-messaging-requirements-00.txt"; site="ftp.ietf.org"; access-type="anon-ftp"; directory="internet-drafts" Content-Type: text/plain Content-ID: <2002-12-18131555.I-D@ietf.org> --OtherAccess-- --NextPart-- _______________________________________________ simple mailing list simple@mailman.dynamicsoft.com http://mailman.dynamicsoft.com/mailman/listinfo/simple From simple-admin@mailman.dynamicsoft.com Fri Dec 20 10:25:01 2002 Received: from mail1.dynamicsoft.com (mail1.dynamicsoft.com [63.113.40.10]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA29224 for ; Fri, 20 Dec 2002 10:25:01 -0500 (EST) Received: from mailman.dynamicsoft.com ([192.168.4.50]) by mail1.dynamicsoft.com (8.12.0.Beta7/8.12.0.Beta7) with ESMTP id gBKFPnKW017574; Fri, 20 Dec 2002 10:25:49 -0500 (EST) Received: from mailman.dynamicsoft.com (localhost [127.0.0.1]) by mailman.dynamicsoft.com (8.9.3+Sun/8.9.3) with ESMTP id KAA18198; Fri, 20 Dec 2002 10:27:04 -0500 (EST) Received: from mgw-x1.nokia.com (mgw-x1.nokia.com [131.228.20.21]) by mailman.dynamicsoft.com (8.9.3+Sun/8.9.3) with ESMTP id KAA18187 for ; Fri, 20 Dec 2002 10:26:57 -0500 (EST) From: krisztian.kiss@nokia.com Received: from esvir01nok.ntc.nokia.com (esvir01nokt.ntc.nokia.com [172.21.143.33]) by mgw-x1.nokia.com (Switch-2.2.1/Switch-2.2.0) with ESMTP id gBKFQA010850 for ; Fri, 20 Dec 2002 17:26:10 +0200 (EET) Received: from esebh003.NOE.Nokia.com (unverified) by esvir01nok.ntc.nokia.com (Content Technologies SMTPRS 4.2.5) with ESMTP id ; Fri, 20 Dec 2002 17:26:56 +0200 Received: from esebh005.NOE.Nokia.com ([172.21.138.86]) by esebh003.NOE.Nokia.com with Microsoft SMTPSVC(5.0.2195.5329); Fri, 20 Dec 2002 17:26:56 +0200 Received: from esebe018.NOE.Nokia.com ([172.21.138.57]) by esebh005.NOE.Nokia.com with Microsoft SMTPSVC(5.0.2195.5329); Fri, 20 Dec 2002 17:26:55 +0200 Received: from trebe003.NOE.Nokia.com ([172.22.232.175]) by esebe018.NOE.Nokia.com with Microsoft SMTPSVC(5.0.2195.5329); Fri, 20 Dec 2002 17:26:54 +0200 X-MimeOLE: Produced By Microsoft Exchange V6.0.6249.0 content-class: urn:content-classes:message MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Subject: RE: [Simple] PUBLISH requirements Message-ID: Thread-Topic: [Simple] PUBLISH requirements Thread-Index: AcKiaj8A1Wm0iMs8TJq75VsvuHEAvQDkTn3A To: , Cc: X-OriginalArrivalTime: 20 Dec 2002 15:26:54.0932 (UTC) FILETIME=[3A4B6940:01C2A83C] Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from quoted-printable to 8bit by mailman.dynamicsoft.com id KAA18187 Sender: simple-admin@mailman.dynamicsoft.com Errors-To: simple-admin@mailman.dynamicsoft.com X-BeenThere: simple@mailman.dynamicsoft.com X-Mailman-Version: 2.0 Precedence: bulk List-Help: List-Post: List-Subscribe: , List-Id: SIP for Presence List-Unsubscribe: , List-Archive: Date: Fri, 20 Dec 2002 17:26:54 +0200 Content-Transfer-Encoding: 8bit Hi All, In order to help to progress the PUBLISH requirements work, here is a collection of requirements as a discussion opener. Comments are more than welcome. REQ1: It must be possible for the PUA to add elements to the presence information as well as remove or modify existing elements of the presence information. REQ2: The publish mechanism must allow a PUA to change only part of the presentity's presence information. For example, a PUA must be able to only publish one single element of the presentity's PIDF document, while the document contains several elements. REQ3: There must be one default content type for the publish mechanism. REQ4: It must be possible for the presentity to publish multimedia contents along with their communication means. REQ5: The publication mechanism must allow publishing from multiple PUAs of a single presentity. REQ6: The PUA must be able to publish to a specific piece of presence, shared among many PUAs (the number of sources must neither be limited nor pre-defined). This means that the published tuples need to be identified across all of the PUAs of a presentity. REQ7: Presence information must be always available. This means that in case the PUAs do not refresh presence information, some information must remain available for watchers, as - for example - the remaining information is hard-state data by nature or soft-state data but it has default value when data expired. REQ8: The PUA must be able to receive feedback about the result of a publishing transaction, the feedback must contain enough information for the principal controlling the presentity to know that the published presence information was successfully composed into the presence document by the Presence Server. Regards, Krisztian > -----Original Message----- > From: ext Jonathan Rosenberg [mailto:jdrosen@dynamicsoft.com] > Sent: Friday, December 13, 2002 7:36 AM > To: Niemi Aki (NET/Espoo) > Cc: simple@mailman.dynamicsoft.com > Subject: Re: [Simple] PUBLISH requirements > > > > > aki.niemi@nokia.com wrote: > > > The discussion in the SIMPLE session in Atlanta lead us towards > > another round of PUBLISH requirements. I think it would be good to > > look at some requirements that might be arising from the fact that > > the dynamics of publishing are distinctly different from > the dynamics > > of notification. > > Yes, I agree. Makes you glad we didn't go for NOTIFY as the > publication > mechanism... > > In order for the composer to make a > > coherent, single presence document out of the information > coming from > > many sources, the composer should be able to identify the published > > information uniquely across all of the PUAs of a presentity. > > The information is needed by others too. A presentity might want to > setup a policy that says "only Joe and Bob can see my cell > phone". That > requires some unique way for the composer to identify which > tuple is the > cell phone. > > > > > For example, if we say that a tuple is the base data unit of > > published presence information, then a specific tuple has to have a > > common ID across all PUAs of a presentity. In other words, the > > tuple-id needs to have semantics associated with it. This way the > > composer can merge two "im-inbox" publications into one single > > presence document tuple. This seems like an additional requirement > > for PIDF when it is used in publishing presence state. > > I think this is a slightly different issue than above. One > requirement > is just identification of the tuples whose scope is broader > than the id > attribute. What you are suggesting here, I think, is almost to define > different classes of tuples. THis way, if I have two PCs, > each of which > has an "im-inbox", the composer could know to combine (or > treat in the > appropriate manner) those two tuples. That seems more of a > slippery slope. > > > > > In addition to this, I think there may also be other requirements > > there related to expiration of state, and the fact that not all > > presence information is wrapped into a element. E.g., the > > presentity level element is not dependent of any > tuples. How > > does one only publish a ? Or remove it? > > Well, PIDF is going to change to allow a document with just a note. I > raised this issue in IMPP and folks were ok with the change. > > Now, to remove a note, you'd presumably publish an empty document. > > That is, the assumption is that, as far as each publication > instance is > concerned, each publication represents the complete presence > state from > that instance. > > -Jonathan R. > > -- > Jonathan D. Rosenberg, Ph.D. 72 Eagle Rock Ave. > Chief Scientist First Floor > dynamicsoft East Hanover, NJ 07936 > jdrosen@dynamicsoft.com FAX: (973) 952-5050 > http://www.jdrosen.net PHONE: (973) 952-5000 > http://www.dynamicsoft.com > > _______________________________________________ > simple mailing list > simple@mailman.dynamicsoft.com > http://mailman.dynamicsoft.com/mailman/listinfo/simple > _______________________________________________ simple mailing list simple@mailman.dynamicsoft.com http://mailman.dynamicsoft.com/mailman/listinfo/simple From simple-admin@mailman.dynamicsoft.com Fri Dec 20 12:06:50 2002 Received: from mail1.dynamicsoft.com (mail1.dynamicsoft.com [63.113.40.10]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA02218 for ; Fri, 20 Dec 2002 12:06:50 -0500 (EST) Received: from mailman.dynamicsoft.com ([192.168.4.50]) by mail1.dynamicsoft.com (8.12.0.Beta7/8.12.0.Beta7) with ESMTP id gBKH7qKW018024; Fri, 20 Dec 2002 12:07:52 -0500 (EST) Received: from mailman.dynamicsoft.com (localhost [127.0.0.1]) by mailman.dynamicsoft.com (8.9.3+Sun/8.9.3) with ESMTP id MAA18540; Fri, 20 Dec 2002 12:09:04 -0500 (EST) Received: from oe-im2.bizmailsrvcs.net (oe-im2pub.managedmail.com [206.46.164.53]) by mailman.dynamicsoft.com (8.9.3+Sun/8.9.3) with ESMTP id MAA18529 for ; Fri, 20 Dec 2002 12:08:02 -0500 (EST) Received: from oe-ismta2.bizmailsrvcs.net ([206.46.164.27]) by oe-im2.bizmailsrvcs.net (InterMail vM.5.01.05.12 201-253-122-126-112-20020820) with ESMTP id <20021220170803.WJNJ2778.oe-im2.bizmailsrvcs.net@oe-ismta2.bizmailsrvcs.net>; Fri, 20 Dec 2002 11:08:03 -0600 Received: from RoselinskyM ([68.6.92.160]) by oe-ismta2.bizmailsrvcs.net (InterMail vM.5.01.05.20 201-253-122-126-120-20021101) with SMTP id <20021220170802.ZSRF3996.oe-ismta2.bizmailsrvcs.net@RoselinskyM>; Fri, 20 Dec 2002 11:08:02 -0600 From: "Milt Roselinsky" To: "Jonathan Rosenberg" Cc: , Subject: RE: [Simple] 3GPP Messaging requirements Message-ID: MIME-Version: 1.0 Content-Type: text/plain; charset="Windows-1252" Content-Transfer-Encoding: 8bit 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.1106 Importance: Normal In-reply-to: <3DFF55D7.8060908@dynamicsoft.com> Sender: simple-admin@mailman.dynamicsoft.com Errors-To: simple-admin@mailman.dynamicsoft.com X-BeenThere: simple@mailman.dynamicsoft.com X-Mailman-Version: 2.0 Precedence: bulk List-Help: List-Post: List-Subscribe: , List-Id: SIP for Presence List-Unsubscribe: , List-Archive: Date: Fri, 20 Dec 2002 09:08:05 -0800 Content-Transfer-Encoding: 8bit > -----Original Message----- > From: simple-admin@mailman.dynamicsoft.com > [mailto:simple-admin@mailman.dynamicsoft.com]On Behalf Of Jonathan > Rosenberg > Sent: Tuesday, December 17, 2002 8:51 AM > To: Milt Roselinsky > Cc: aki.niemi@nokia.com; simple@mailman.dynamicsoft.com > Subject: Re: [Simple] 3GPP Messaging requirements > > > > > Milt Roselinsky wrote: > >>>The missing message filter criteria are message type and recipient’s > >>>presence status. > >> > >>What is message type? > > > > > > immediate or session based message > > Just to be sure we are on the same page with terminology, "immediate" is > page mode (i.e, RFC 3428, the MESSAGE method), and session-based are as > per draft-campbell-simple-im-sessions? Session-based is covered well by draft-campbell-simple-im-sessions. I think there are still some outstanding issues WRT using MESSAGE method for immediate messaging. It works well for short messages but for larger multimedia messages there are still a lot of outstanding issues and questions. Best regards, Milt _______________________________________________ simple mailing list simple@mailman.dynamicsoft.com http://mailman.dynamicsoft.com/mailman/listinfo/simple From simple-admin@mailman.dynamicsoft.com Mon Dec 23 01:14:07 2002 Received: from mail1.dynamicsoft.com (mail1.dynamicsoft.com [63.113.40.10]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id BAA12488 for ; Mon, 23 Dec 2002 01:14:07 -0500 (EST) Received: from mailman.dynamicsoft.com ([192.168.4.50]) by mail1.dynamicsoft.com (8.12.0.Beta7/8.12.0.Beta7) with ESMTP id gBN6F2KW023383; Mon, 23 Dec 2002 01:15:02 -0500 (EST) Received: from mailman.dynamicsoft.com (localhost [127.0.0.1]) by mailman.dynamicsoft.com (8.9.3+Sun/8.9.3) with ESMTP id BAA28561; Mon, 23 Dec 2002 01:16:07 -0500 (EST) Received: from mail3.dynamicsoft.com (mail3.dynamicsoft.com [63.113.44.69]) by mailman.dynamicsoft.com (8.9.3+Sun/8.9.3) with ESMTP id BAA28550 for ; Mon, 23 Dec 2002 01:15:23 -0500 (EST) Received: from dynamicsoft.com ([63.113.46.53]) by mail3.dynamicsoft.com (8.12.1/8.12.1) with ESMTP id gBN6FOYH021408; Mon, 23 Dec 2002 01:15:24 -0500 (EST) Message-ID: <3E06A9F9.6070808@dynamicsoft.com> From: Jonathan Rosenberg Organization: dynamicsoft User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.1) Gecko/20020826 X-Accept-Language: en-us, en MIME-Version: 1.0 To: Milt Roselinsky CC: aki.niemi@nokia.com, simple@mailman.dynamicsoft.com Subject: Re: [Simple] 3GPP Messaging requirements References: Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Sender: simple-admin@mailman.dynamicsoft.com Errors-To: simple-admin@mailman.dynamicsoft.com X-BeenThere: simple@mailman.dynamicsoft.com X-Mailman-Version: 2.0 Precedence: bulk List-Help: List-Post: List-Subscribe: , List-Id: SIP for Presence List-Unsubscribe: , List-Archive: Date: Mon, 23 Dec 2002 01:15:21 -0500 Content-Transfer-Encoding: 7bit Milt Roselinsky wrote: > > Session-based is covered well by draft-campbell-simple-im-sessions. > > I think there are still some outstanding issues WRT using MESSAGE method > for immediate messaging. It works well for short messages but for larger > multimedia messages there are still a lot of outstanding issues and > questions. For larger messages, we have several answers: 1. use session mode, 2. use content indirection 3. congestion safety -Jonathan R. -- Jonathan D. Rosenberg, Ph.D. 72 Eagle Rock Ave. Chief Scientist First Floor dynamicsoft East Hanover, NJ 07936 jdrosen@dynamicsoft.com FAX: (973) 952-5050 http://www.jdrosen.net PHONE: (973) 952-5000 http://www.dynamicsoft.com _______________________________________________ simple mailing list simple@mailman.dynamicsoft.com http://mailman.dynamicsoft.com/mailman/listinfo/simple From simple-admin@mailman.dynamicsoft.com Wed Dec 25 23:34:09 2002 Received: from mail1.dynamicsoft.com (mail1.dynamicsoft.com [63.113.40.10]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id XAA25593 for ; Wed, 25 Dec 2002 23:34:08 -0500 (EST) Received: from mailman.dynamicsoft.com ([192.168.4.50]) by mail1.dynamicsoft.com (8.12.0.Beta7/8.12.0.Beta7) with ESMTP id gBQ4Ys67005779; Wed, 25 Dec 2002 23:34:55 -0500 (EST) Received: from mailman.dynamicsoft.com (localhost [127.0.0.1]) by mailman.dynamicsoft.com (8.9.3+Sun/8.9.3) with ESMTP id XAA11371; Wed, 25 Dec 2002 23:36:06 -0500 (EST) Received: from himalaya.scicmp.com ([203.200.79.36]) by mailman.dynamicsoft.com (8.9.3+Sun/8.9.3) with SMTP id XAA11360 for ; Wed, 25 Dec 2002 23:35:46 -0500 (EST) Received: from mx1.scicmp.com ([10.130.0.5]) by himalaya.scicmp.com (NAVGW 2.5.2.12) with SMTP id M2002122610053104178 ; Thu, 26 Dec 2002 10:05:31 +0530 Received: from scicmp.com (kanchenjunga [10.140.13.178]) by mx1.scicmp.com (8.9.3/8.8.7) with ESMTP id KAA22597; Thu, 26 Dec 2002 10:11:54 +0530 Message-ID: <3E0A87A6.6309A00F@scicmp.com> From: Sudipta Ghosh Organization: Scicom Infotech Pvt. Ltd. (Scicom) X-Mailer: Mozilla 4.79 [en] (Windows NT 5.0; U) X-Accept-Language: en,pdf MIME-Version: 1.0 To: sipforum , simple , Jonathan Rosenberg , aki.niemi@nokia.com CC: krisztian.kiss@nokia.com, Jean.Chastain@wcom.com Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Subject: [Simple] Transaction Layer doubt Sender: simple-admin@mailman.dynamicsoft.com Errors-To: simple-admin@mailman.dynamicsoft.com X-BeenThere: simple@mailman.dynamicsoft.com X-Mailman-Version: 2.0 Precedence: bulk List-Help: List-Post: List-Subscribe: , List-Id: SIP for Presence List-Unsubscribe: , List-Archive: Date: Thu, 26 Dec 2002 10:07:58 +0530 Content-Transfer-Encoding: 7bit Hi, I have one doubt regarding Transaction Layer. According to SIP RFC 3261. Transaction Layer retransmits sip request if it doesnt get the response for that method. The rule of re-transmission is given in RFC. After certain time Transaction Layer will inform the Transaction User(TU) about timeout. Now my question are. 1.A UAC will retransmit a request to proxy if it didnt get the response. Proxy will retransmit the request to UAS. (If the UAS is in the same domian) In proxy retransmission of request will be made form its Transaction Layer but proxy will receive the same request from UAC. What Proxy will do when it gets same request from UAC? Why retransmission of request is also included in PROXY?(UAC retransmits a request if it doesnt get the response) 2.I have noticed that MSN Messenger doesnt retransmit MESSAGE request when it doesn't get the response. This is the case when I am sending a MESSAGE to offline user.In this case MSN tells about the failure of message delivery. sudipta -- *********************************************** System Executive Scicom Infotech Pvt. Ltd. (Scicom) A - 67, Sector - 57 Noida - 201 301 UP ********************************************** _______________________________________________ simple mailing list simple@mailman.dynamicsoft.com http://mailman.dynamicsoft.com/mailman/listinfo/simple From simple-admin@mailman.dynamicsoft.com Thu Dec 26 12:53:51 2002 Received: from mail1.dynamicsoft.com (mail1.dynamicsoft.com [63.113.40.10]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA13415 for ; Thu, 26 Dec 2002 12:53:51 -0500 (EST) Received: from mailman.dynamicsoft.com ([192.168.4.50]) by mail1.dynamicsoft.com (8.12.0.Beta7/8.12.0.Beta7) with ESMTP id gBQHsn67006816; Thu, 26 Dec 2002 12:54:50 -0500 (EST) Received: from mailman.dynamicsoft.com (localhost [127.0.0.1]) by mailman.dynamicsoft.com (8.9.3+Sun/8.9.3) with ESMTP id MAA13930; Thu, 26 Dec 2002 12:56:04 -0500 (EST) Received: from mail3.dynamicsoft.com (mail3.dynamicsoft.com [63.113.44.69]) by mailman.dynamicsoft.com (8.9.3+Sun/8.9.3) with ESMTP id MAA13919 for ; Thu, 26 Dec 2002 12:55:20 -0500 (EST) Received: from dynamicsoft.com ([63.113.46.53]) by mail3.dynamicsoft.com (8.12.1/8.12.1) with ESMTP id gBQHtNYH022668; Thu, 26 Dec 2002 12:55:23 -0500 (EST) Message-ID: <3E0B4288.7050005@dynamicsoft.com> From: Jonathan Rosenberg Organization: dynamicsoft User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.1) Gecko/20020826 X-Accept-Language: en-us, en MIME-Version: 1.0 To: mmusic@ietf.org, simple@mailman.dynamicsoft.com Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Subject: [Simple] new I-D on proposed changes to comedia Sender: simple-admin@mailman.dynamicsoft.com Errors-To: simple-admin@mailman.dynamicsoft.com X-BeenThere: simple@mailman.dynamicsoft.com X-Mailman-Version: 2.0 Precedence: bulk List-Help: List-Post: List-Subscribe: , List-Id: SIP for Presence List-Unsubscribe: , List-Archive: Date: Thu, 26 Dec 2002 12:55:20 -0500 Content-Transfer-Encoding: 7bit Folks, As you may recall, Ben Campbell had posted an I-D on the usage of CPIM over TCP for the IM session protocol (http://www.ietf.org/internet-drafts/draft-campbell-simple-cpimmsg-sessions-00.txt). There was good support for this, but it became clear on the list that the proposed usage of comedia was problematic in the presence of intermediaries. During the mmusic session, I asked for a months time to investigate the problem and come up with a concrete proposal, whether it was changes to comedia, or a separate protocol. I have worked this with Ben and Paul Kyzivat, and the result is a set of proposed changes to comedia. Our motiviations for these changes, along with the proposed changes themselves, are documented in an I-D I just submitted. Until it appears (and it will be a while, because the I-D editor is on vacation), you can pick it up at: http://www.jdrosen.net/papers/draft-rosenberg-mmusic-comedia-fix-00.txt http://www.jdrosen.net/papers/draft-rosenberg-mmusic-comedia-fix-00.html I have cross-posted to simple to make them aware of this draft, but discussion should proceed on mmusic. Thanks, Jonathan R. -- Jonathan D. Rosenberg, Ph.D. 72 Eagle Rock Ave. Chief Scientist First Floor dynamicsoft East Hanover, NJ 07936 jdrosen@dynamicsoft.com FAX: (973) 952-5050 http://www.jdrosen.net PHONE: (973) 952-5000 http://www.dynamicsoft.com _______________________________________________ simple mailing list simple@mailman.dynamicsoft.com http://mailman.dynamicsoft.com/mailman/listinfo/simple From simple-admin@mailman.dynamicsoft.com Fri Dec 27 07:19:54 2002 Received: from mail1.dynamicsoft.com (mail1.dynamicsoft.com [63.113.40.10]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA06643 for ; Fri, 27 Dec 2002 07:19:54 -0500 (EST) Received: from mailman.dynamicsoft.com ([192.168.4.50]) by mail1.dynamicsoft.com (8.12.0.Beta7/8.12.0.Beta7) with ESMTP id gBRCKp67008150; Fri, 27 Dec 2002 07:20:51 -0500 (EST) Received: from mailman.dynamicsoft.com (localhost [127.0.0.1]) by mailman.dynamicsoft.com (8.9.3+Sun/8.9.3) with ESMTP id HAA17094; Fri, 27 Dec 2002 07:22:07 -0500 (EST) Received: from hss.hns.com ([164.164.94.118]) by mailman.dynamicsoft.com (8.9.3+Sun/8.9.3) with ESMTP id HAA17083 for ; Fri, 27 Dec 2002 07:21:14 -0500 (EST) From: hbhondwe@hss.hns.com Received: from sampark.hss.hns.com (sampark [139.85.229.22]) by hss.hns.com (8.11.6/8.11.2) with SMTP id gBRBu9i21658; Fri, 27 Dec 2002 17:26:11 +0530 Received: by sampark.hss.hns.com(Lotus SMTP MTA Internal build v4.6.2 (651.2 6-10-1998)) id 65256C9C.00436B12 ; Fri, 27 Dec 2002 17:46:23 +0530 X-Lotus-FromDomain: HSSBLR To: sip@ietf.org cc: adam@dynamicsoft.com, simple@mailman.dynamicsoft.com Message-ID: <65256C9C.00436AD1.00@sampark.hss.hns.com> Mime-Version: 1.0 Content-type: text/plain; charset=us-ascii Content-Disposition: inline Subject: [Simple] Comments on draft-roach-sip-list-template-00.txt Sender: simple-admin@mailman.dynamicsoft.com Errors-To: simple-admin@mailman.dynamicsoft.com X-BeenThere: simple@mailman.dynamicsoft.com X-Mailman-Version: 2.0 Precedence: bulk List-Help: List-Post: List-Subscribe: , List-Id: SIP for Presence List-Unsubscribe: , List-Archive: Date: Fri, 27 Dec 2002 17:46:21 +0530 Hi, Some comments on this draft, assuming that this draft is open for comments. Not sure if this should go to Simple or Sip mailing list. 1)Section 4.3 Constructing Coherent Resource State, states "The resource list subscriber maintains a table for each resource list. The table contains a row for each resource in the resource list." and then it states that a version number is associated with each row of the resource list table. Why should a version be associated with each resource of a resource list? Should it not be associated with the resource list table instead? RFC 3265 states in section 4.3.2 State Deltas, "Any event package that supports delta changes to states MUST include a version number that increases by exactly one for each NOTIFY transaction in a subscription. ". 2)Section 4.3 (of the draft) states that when the version number jumps, the document received should be processed. I presume that "processing" implies what is elaborated in the same section later on. Extract from sec 4.3 of the draft: "If the value in the document is more than one higher than the local version number, the local version number is set to the value in the new document, the document is processed, and the .list subscriber SHOULD generate a refresh request to trigger a full state notification." whereas RFC 3265 in sec 4.3.2 says that when version number jumps , the Notify message can be ignored. Extract from RFC 3265, sec 4.3.2: "If a NOTIFY arrives that has a version number that is incremented by more than one, the subscriber knows that a state delta has been missed; it ignores the NOTIFY message containing the state delta (except for the version number, which it retains to detect message loss), and re-sends a SUBSCRIBE to force a NOTIFY containing a complete state snapshot. 3)Should the .list subscriber generate a refresh request even when the version is not consecutive AND "State" header indicates full state? The .list subcriber may have lost some intermediate notifications, but has now received full state. It can very well update its local version to the new version without doing any refresh. If the "State" indicates partial, however, then a refresh request is called for. thanks Harsh Bhondwe This message is proprietary to Hughes Software Systems Limited (HSS) and is intended solely for the use of the individual to whom it is addressed. It may contain privileged or confidential information and should not be circulated or used for any purpose other than for what it is intended. If you have received this message in error, please notify the originator immediately. If you are not the intended recipient, you are notified that you are strictly prohibited from using, copying, altering, or disclosing the contents of this message. HSS accepts no responsibility for loss or damage arising from the use of the information transmitted by this email including damage from virus. _______________________________________________ simple mailing list simple@mailman.dynamicsoft.com http://mailman.dynamicsoft.com/mailman/listinfo/simple From simple-admin@mailman.dynamicsoft.com Sat Dec 28 01:35:13 2002 Received: from mail1.dynamicsoft.com (mail1.dynamicsoft.com [63.113.40.10]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id BAA21589 for ; Sat, 28 Dec 2002 01:35:13 -0500 (EST) Received: from mailman.dynamicsoft.com ([192.168.4.50]) by mail1.dynamicsoft.com (8.12.0.Beta7/8.12.0.Beta7) with ESMTP id gBS6Zu67009870; Sat, 28 Dec 2002 01:35:56 -0500 (EST) Received: from mailman.dynamicsoft.com (localhost [127.0.0.1]) by mailman.dynamicsoft.com (8.9.3+Sun/8.9.3) with ESMTP id BAA20396; Sat, 28 Dec 2002 01:37:04 -0500 (EST) Received: from bdsl.greycouncil.com (bdsl.66.12.12.130.gte.net [66.12.12.130]) by mailman.dynamicsoft.com (8.9.3+Sun/8.9.3) with ESMTP id BAA20385 for ; Sat, 28 Dec 2002 01:36:11 -0500 (EST) Received: from softarmor.com (bdsl.greycouncil.com [127.0.0.1]) by bdsl.greycouncil.com (8.12.5/8.12.5) with ESMTP id gBS6a18W003718; Sat, 28 Dec 2002 00:36:03 -0600 Message-ID: <3E0D464A.1030507@softarmor.com> From: Dean Willis User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.2.1) Gecko/20021130 X-Accept-Language: en-us, en MIME-Version: 1.0 To: krisztian.kiss@nokia.com CC: jdrosen@dynamicsoft.com, aki.niemi@nokia.com, simple@mailman.dynamicsoft.com Subject: Re: [Simple] PUBLISH requirements References: In-Reply-To: X-Enigmail-Version: 0.65.2.0 X-Enigmail-Supports: pgp-inline, pgp-mime Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Sender: simple-admin@mailman.dynamicsoft.com Errors-To: simple-admin@mailman.dynamicsoft.com X-BeenThere: simple@mailman.dynamicsoft.com X-Mailman-Version: 2.0 Precedence: bulk List-Help: List-Post: List-Subscribe: , List-Id: SIP for Presence List-Unsubscribe: , List-Archive: Date: Sat, 28 Dec 2002 00:35:54 -0600 Content-Transfer-Encoding: 7bit Krisztian "published" some requirements: > REQ3: There must be one default content type for the publish > mechanism. I don't think I understand this one. Are you saying that, for example, if we use MIME for the body, that if the body doesn't specifically SAY that it is some particular MIME type, that we should assume it is anyhow? > REQ4: It must be possible for the presentity to publish multimedia > contents along with their communication means. I don't think I understand this one either. Can you give an example? > REQ7: Presence information must be always available. This means that > in case the PUAs do not refresh presence information, some > information must remain available for watchers, as - for example - > the remaining information is hard-state data by nature or soft-state > data but it has default value when data expired. I think what you mean here is that the invocation of the publishing mechanism should not, by default, erase any previously published information. For example, if many different tuples exist for a presentity, that publishing a single new tuple should not normally cause the other previously published tuples to be discarded. Right? -- Dean _______________________________________________ simple mailing list simple@mailman.dynamicsoft.com http://mailman.dynamicsoft.com/mailman/listinfo/simple