From extest-admin@lists.bell-labs.com Sat Feb 1 05:20:04 2003 Received: from share.research.bell-labs.com (share.research.bell-labs.com [204.178.16.58]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id FAA03657 for ; Sat, 1 Feb 2003 05:20:04 -0500 (EST) Received: from share.research.bell-labs.com (localhost [127.0.0.1]) by share.research.bell-labs.com (8.11.6/8.11.6) with ESMTP id h11ANg218101 for ; Sat, 1 Feb 2003 05:23:47 -0500 Date: Sat, 1 Feb 2003 05:23:47 -0500 Message-Id: <200302011023.h11ANg218101@share.research.bell-labs.com> Subject: lists.bell-labs.com mailing list memberships reminder From: mailman-owner@lists.bell-labs.com To: spirits-archive@ietf.org X-No-Archive: yes X-Ack: no Sender: extest-admin@lists.bell-labs.com Errors-To: extest-admin@lists.bell-labs.com X-BeenThere: extest@lists.bell-labs.com X-Mailman-Version: 2.0.8 Precedence: bulk This is a reminder, sent out once a month, about your lists.bell-labs.com mailing list memberships. It includes your subscription info and how to use it to change it or unsubscribe from a list. You can visit the URLs to change your membership status or configuration, including unsubscribing, setting digest-style delivery or disabling delivery altogether (e.g., for a vacation), and so on. In addition to the URL interfaces, you can also use email to make such changes. For more info, send a message to the '-request' address of the list (for example, spirits-request@lists.bell-labs.com) containing just the word 'help' in the message body, and an email message will be sent to you with instructions. If you have questions, problems, comments, etc, send them to mailman-owner@lists.bell-labs.com. Thanks! Passwords for spirits-archive@lists.ietf.org: List Password // URL ---- -------- spirits@lists.bell-labs.com unmora http://lists.bell-labs.com/mailman/options/spirits/spirits-archive%40lists.ietf.org From spirits-admin@lists.bell-labs.com Tue Feb 4 12:46:38 2003 Received: from share.research.bell-labs.com (share.research.bell-labs.com [204.178.16.58]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA29619 for ; Tue, 4 Feb 2003 12:46:37 -0500 (EST) Received: from share.research.bell-labs.com (localhost [127.0.0.1]) by share.research.bell-labs.com (8.11.6/8.11.6) with ESMTP id h14Ho2230463; Tue, 4 Feb 2003 12:50:02 -0500 Received: from dirty.research.bell-labs.com (ns1.research.bell-labs.com [204.178.16.6]) by share.research.bell-labs.com (8.11.6/8.11.6) with ESMTP id h14HnJ230441 for ; Tue, 4 Feb 2003 12:49:19 -0500 Received: from lists.bell-labs.com (H-135-104-27-211.research.bell-labs.com [135.104.27.211]) by dirty.research.bell-labs.com (8.12.5/8.12.5) with ESMTP id h14HnAhN023010 for ; Tue, 4 Feb 2003 12:49:10 -0500 (EST) Received: by lists.bell-labs.com (Postfix) id 41C95443A5; Tue, 4 Feb 2003 12:49:05 -0500 (EST) Delivered-To: spirits@sunny.research.bell-labs.com Received: from grubby.research.bell-labs.com (guard.research.bell-labs.com [135.104.2.9]) by lists.bell-labs.com (Postfix) with ESMTP id 18911443A4 for ; Tue, 4 Feb 2003 12:49:05 -0500 (EST) Received: from ih2mail.ih.lucent.com (ih2mail.ih.lucent.com [135.1.241.39]) by grubby.research.bell-labs.com (8.11.6/8.11.6) with ESMTP id h14Hn3Y67835 for ; Tue, 4 Feb 2003 12:49:03 -0500 (EST) Received: from lucent.com by ih2mail.ih.lucent.com (8.8.8+Sun/EMS-1.5 sol2) id LAA10221; Tue, 4 Feb 2003 11:49:00 -0600 (CST) Message-ID: <3E3FFCF4.8050801@lucent.com> From: "Vijay K. Gurbani" Organization: Lucent Technologies, Inc./Bell Laboratories 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: "Vijay K. Gurbani" Cc: SPIRITS list Subject: Re: [SPIRITS] Representing non-call related events References: <3E3AF0CD.9020107@lucent.com> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Sender: spirits-admin@lists.bell-labs.com Errors-To: spirits-admin@lists.bell-labs.com X-BeenThere: spirits@lists.bell-labs.com X-Mailman-Version: 2.0.8 Precedence: bulk List-Help: List-Post: List-Subscribe: , List-Id: List-Unsubscribe: , List-Archive: Date: Tue, 04 Feb 2003 11:48:36 -0600 Content-Transfer-Encoding: 7bit Folks: Regarding the discussion below, it was suggested to me in a private email that the CUSF functional entity of IN-CS2 be looked into. Is there anyone on the list familiar with this and willing to pitch in some time? Any discussion (and help) will be extremely fruitful, I think... Thanks, - vijay Vijay K. Gurbani wrote: > Folks: > > I want to start a discussion about how to best represent non-call > related events in the SPIRITS XML payload. > > Non-call related events include those concerned with mobility, > location, SMS, etc. Note that no DP is involved here; in fact, > SPIRITS has a Event token called 'spirits-user-prof' for these > types of events. > > One way to represent these events to have a specific element > called for such SUPplementary services. Thus, in order > to transform a SMS into an IM, the SUBSCRIBE payload could > conceivably contain: > > > > Notify > 16302240216 > > > However, that puts us in the dubious position of specifying all > the possible supplementary services in SPIRITS -- which is > definitely NOT what we want to do. One way to combat that problem > is to say that the value of "app" attribute is a token, the details > and semantics of which are dependent on the token. > > How do we handle location? Maybe we can scour geopriv for some > answers (see > http://www.ietf.org/internet-drafts/draft-daviel-html-geo-tag-05.txt) > as well as Daniel Moreno's draft on mobility events management > (http://www.ietf.org/internet-drafts/draft-ietf-spirits-mobility-00.txt) > > Any other ideas? Any thoughts would be appreciated. > > Thanks, > > - vijay -- Vijay K. Gurbani vkg@{lucent.com,research.bell-labs.com,acm.org} Wireless Networks Group/Internet Software and Services Lucent Technologies/Bell Labs Innovations, 2000 Lucent Lane, Rm 6G-440 Naperville, Illinois 60566 Voice: +1 630 224 0216 _______________________________________________ SPIRITS mailing list SPIRITS@lists.bell-labs.com http://lists.bell-labs.com/mailman/listinfo/spirits From spirits-admin@lists.bell-labs.com Tue Feb 4 22:55:34 2003 Received: from share.research.bell-labs.com (share.research.bell-labs.com [204.178.16.58]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id WAA14514 for ; Tue, 4 Feb 2003 22:55:33 -0500 (EST) Received: from share.research.bell-labs.com (localhost [127.0.0.1]) by share.research.bell-labs.com (8.11.6/8.11.6) with ESMTP id h153x3201960; Tue, 4 Feb 2003 22:59:03 -0500 Received: from dirty.research.bell-labs.com (dirty.research.bell-labs.com [204.178.16.6]) by share.research.bell-labs.com (8.11.6/8.11.6) with ESMTP id h153wO201947 for ; Tue, 4 Feb 2003 22:58:24 -0500 Received: from lists.bell-labs.com (H-135-104-27-211.research.bell-labs.com [135.104.27.211]) by dirty.research.bell-labs.com (8.12.5/8.12.5) with ESMTP id h153wFhN028234 for ; Tue, 4 Feb 2003 22:58:15 -0500 (EST) Received: by lists.bell-labs.com (Postfix) id 2AFD7443A5; Tue, 4 Feb 2003 22:58:10 -0500 (EST) Delivered-To: spirits@sunny.research.bell-labs.com Received: from grubby.research.bell-labs.com (guard.research.bell-labs.com [135.104.2.9]) by lists.bell-labs.com (Postfix) with ESMTP id 0507F443A4 for ; Tue, 4 Feb 2003 22:58:09 -0500 (EST) Received: from dusty.research.bell-labs.com (dusty.research.bell-labs.com [135.104.2.7]) by grubby.research.bell-labs.com (8.11.6/8.11.6) with ESMTP id h153w6Y13569 for ; Tue, 4 Feb 2003 22:58:06 -0500 (EST) Received: from hindon.hss.co.in ([202.54.26.202]) by dusty.research.bell-labs.com (8.12.6/8.12.6) with ESMTP id h153tHoJ097037 for ; Tue, 4 Feb 2003 22:55:18 -0500 (EST) Received: from hindon.hss.co.in (localhost [127.0.0.1]) by hindon.hss.co.in (8.10.0/8.10.0) with ESMTP id h153uWj10760 for ; Wed, 5 Feb 2003 09:26:32 +0530 (IST) Received: from ultra.hss.co.in (ultra.hss.hns.com [192.168.100.5]) by hindon.hss.co.in (8.10.0/8.10.0) with ESMTP id h153uVM10755; Wed, 5 Feb 2003 09:26:31 +0530 (IST) Received: from sandesh.hss.hns.com (localhost [127.0.0.1]) by ultra.hss.co.in (8.10.0/8.10.0) with SMTP id h153wrh11681; Wed, 5 Feb 2003 09:28:53 +0530 (IST) Received: by sandesh.hss.hns.com(Lotus SMTP MTA v4.6.3 (733.2 10-16-1998)) id 65256CC4.00151533 ; Wed, 5 Feb 2003 09:20:16 +0530 X-Lotus-FromDomain: HSS From: dmalhotra@hss.hns.com To: "Vijay K. Gurbani" Cc: "Vijay K. Gurbani" , SPIRITS list Message-ID: <65256CC4.00151330.00@sandesh.hss.hns.com> Subject: Re: [SPIRITS] Representing non-call related events Mime-Version: 1.0 Content-type: text/plain; charset=us-ascii Content-Disposition: inline Sender: spirits-admin@lists.bell-labs.com Errors-To: spirits-admin@lists.bell-labs.com X-BeenThere: spirits@lists.bell-labs.com X-Mailman-Version: 2.0.8 Precedence: bulk List-Help: List-Post: List-Subscribe: , List-Id: List-Unsubscribe: , List-Archive: Date: Wed, 5 Feb 2003 09:20:10 +0530 Vijay, Are you trying to define the way supplementary services shall work in the SPIRITS model ? Regards Dhiraj "Vijay K. Gurbani" on 02/04/2003 11:18:36 PM To: "Vijay K. Gurbani" cc: SPIRITS list (bcc: Dhiraj Malhotra/HSS) Subject: Re: [SPIRITS] Representing non-call related events Folks: Regarding the discussion below, it was suggested to me in a private email that the CUSF functional entity of IN-CS2 be looked into. Is there anyone on the list familiar with this and willing to pitch in some time? Any discussion (and help) will be extremely fruitful, I think... Thanks, - vijay Vijay K. Gurbani wrote: > Folks: > > I want to start a discussion about how to best represent non-call > related events in the SPIRITS XML payload. > > Non-call related events include those concerned with mobility, > location, SMS, etc. Note that no DP is involved here; in fact, > SPIRITS has a Event token called 'spirits-user-prof' for these > types of events. > > One way to represent these events to have a specific element > called for such SUPplementary services. Thus, in order > to transform a SMS into an IM, the SUBSCRIBE payload could > conceivably contain: > > > > Notify > 16302240216 > > > However, that puts us in the dubious position of specifying all > the possible supplementary services in SPIRITS -- which is > definitely NOT what we want to do. One way to combat that problem > is to say that the value of "app" attribute is a token, the details > and semantics of which are dependent on the token. > > How do we handle location? Maybe we can scour geopriv for some > answers (see > http://www.ietf.org/internet-drafts/draft-daviel-html-geo-tag-05.txt) > as well as Daniel Moreno's draft on mobility events management > (http://www.ietf.org/internet-drafts/draft-ietf-spirits-mobility-00.txt) > > Any other ideas? Any thoughts would be appreciated. > > Thanks, > > - vijay -- Vijay K. Gurbani vkg@{lucent.com,research.bell-labs.com,acm.org} Wireless Networks Group/Internet Software and Services Lucent Technologies/Bell Labs Innovations, 2000 Lucent Lane, Rm 6G-440 Naperville, Illinois 60566 Voice: +1 630 224 0216 _______________________________________________ SPIRITS mailing list SPIRITS@lists.bell-labs.com http://lists.bell-labs.com/mailman/listinfo/spirits _______________________________________________ SPIRITS mailing list SPIRITS@lists.bell-labs.com http://lists.bell-labs.com/mailman/listinfo/spirits From spirits-admin@lists.bell-labs.com Wed Feb 5 04:39:30 2003 Received: from share.research.bell-labs.com (share.research.bell-labs.com [204.178.16.58]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA15355 for ; Wed, 5 Feb 2003 04:39:30 -0500 (EST) Received: from share.research.bell-labs.com (localhost [127.0.0.1]) by share.research.bell-labs.com (8.11.6/8.11.6) with ESMTP id h159h2204618; Wed, 5 Feb 2003 04:43:02 -0500 Received: from dirty.research.bell-labs.com (ns1.research.bell-labs.com [204.178.16.6]) by share.research.bell-labs.com (8.11.6/8.11.6) with ESMTP id h159g2204605 for ; Wed, 5 Feb 2003 04:42:02 -0500 Received: from lists.bell-labs.com (H-135-104-27-211.research.bell-labs.com [135.104.27.211]) by dirty.research.bell-labs.com (8.12.5/8.12.5) with ESMTP id h159frhN030610 for ; Wed, 5 Feb 2003 04:41:53 -0500 (EST) Received: by lists.bell-labs.com (Postfix) id AC65F443A5; Wed, 5 Feb 2003 04:41:48 -0500 (EST) Delivered-To: spirits@sunny.research.bell-labs.com Received: from scummy.research.bell-labs.com (guard.research.bell-labs.com [135.104.2.10]) by lists.bell-labs.com (Postfix) with ESMTP id 8630C443A4 for ; Wed, 5 Feb 2003 04:41:48 -0500 (EST) Received: from dusty.research.bell-labs.com (dusty.research.bell-labs.com [135.104.2.7]) by scummy.research.bell-labs.com (8.11.6/8.11.6) with ESMTP id h159fkI16745 for ; Wed, 5 Feb 2003 04:41:46 -0500 (EST) Received: from p-mail2 (p-mail2.rd.francetelecom.com [193.49.124.32]) by dusty.research.bell-labs.com (8.12.6/8.12.6) with SMTP id h159cuoJ027409 for ; Wed, 5 Feb 2003 04:38:59 -0500 (EST) Received: from parsmtp2.rd.francetelecom.com ([10.193.117.129]) by 192.144.74.32 with InterScan Messaging Security Suite; Wed, 05 Feb 2003 10:46:01 +0100 Received: from parmhs2.rd.francetelecom.fr ([10.193.117.61]) by parsmtp2.rd.francetelecom.com with Microsoft SMTPSVC(5.0.2195.5329); Wed, 5 Feb 2003 10:41:27 +0100 content-class: urn:content-classes:message MIME-Version: 1.0 Content-Type: text/plain; charset="US-ASCII" Subject: RE: [SPIRITS] Representing non-call related events X-MimeOLE: Produced By Microsoft Exchange V6.0.6375.0 Message-ID: <448914041F29D7499FA5F0B8ED1C708783B452@parmhs2.rd.francetelecom.fr> Thread-Topic: [SPIRITS] Representing non-call related events Thread-Index: AcLMds/pLaOqNHPWTgC0Hw3+I2Y9JgAfvAPw From: "CHATRAS Bruno FTRD/DAC/ISS" To: "Vijay K. Gurbani" Cc: "SPIRITS list" X-OriginalArrivalTime: 05 Feb 2003 09:41:27.0146 (UTC) FILETIME=[C0FC84A0:01C2CCFA] Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from quoted-printable to 8bit by share.research.bell-labs.com id h159g3204606 Sender: spirits-admin@lists.bell-labs.com Errors-To: spirits-admin@lists.bell-labs.com X-BeenThere: spirits@lists.bell-labs.com X-Mailman-Version: 2.0.8 Precedence: bulk List-Help: List-Post: List-Subscribe: , List-Id: List-Unsubscribe: , List-Archive: Date: Wed, 5 Feb 2003 10:41:25 +0100 Content-Transfer-Encoding: 8bit Some thoughts about the CUSF! Three modes of operations have been defined for the CUSF (See ITU Q.1238.7): 1) For relaying ROSE APDUs to/from an ISDN terminal 2) For triggering an IN service during the execution of a non-call related supplementary service (e.g.; CCBS) 3) For relaying USI information to/from an ISDN terminal Only the first two modes seem to be relevant for this discussion. On both cases, a BCUSM - which includes a few DPs - is involved. The main difference between the two options is the location of the supplementary service execution. In the first case, the supplementary service is executed in the SCF, the CUSF acts almost as a transparent relay. In the second case, the supplementary service is executed by the switch. The CUSF is used to enable an IN service to incluence the processing of the supplementary service (e.g.; modify the called party number in a CCBS-Request), just like the SSF does in a call related context. The first option is not appropriate for SMS or Mobility Management are these "services" - unlike ISDN supplementary services - are generally not implemented using ROSE. The second option would make sense. However, this would require extensions to the protocol as the INAP operations used by the CUSF (e.g.; EventReportBCUSM)do not include SMS or MM-related parameters. It is interesting to note that GSM/UMTS standards do not use of the CUSF for SMS. They use a dedicated state model, with SMS-specific DPs. The INAP operations are not those defined for the CUSF but are also specific to the SMS service. I hope this helps. Bruno > -----Message d'origine----- > De : Vijay K. Gurbani [mailto:vkg@lucent.com] > Envoye : mardi 4 fevrier 2003 18:49 > A : Vijay K. Gurbani > Cc : SPIRITS list > Objet : Re: [SPIRITS] Representing non-call related events > > > Folks: > > Regarding the discussion below, it was suggested to me in a private > email that the CUSF functional entity of IN-CS2 be looked into. > > Is there anyone on the list familiar with this and willing to pitch > in some time? Any discussion (and help) will be extremely fruitful, I > think... > > Thanks, > > - vijay > > Vijay K. Gurbani wrote: > > Folks: > > > > I want to start a discussion about how to best represent non-call > > related events in the SPIRITS XML payload. > > > > Non-call related events include those concerned with mobility, > > location, SMS, etc. Note that no DP is involved here; in fact, > > SPIRITS has a Event token called 'spirits-user-prof' for these > > types of events. > > > > One way to represent these events to have a specific element > > called for such SUPplementary services. Thus, in order > > to transform a SMS into an IM, the SUBSCRIBE payload could > > conceivably contain: > > > > > > > > Notify > > > 16302240216 > > > > > > However, that puts us in the dubious position of specifying all > > the possible supplementary services in SPIRITS -- which is > > definitely NOT what we want to do. One way to combat that problem > > is to say that the value of "app" attribute is a token, the details > > and semantics of which are dependent on the token. > > > > How do we handle location? Maybe we can scour geopriv for some > > answers (see > > http://www.ietf.org/internet-drafts/draft-daviel-html-geo-tag-05.txt) > as well as Daniel Moreno's draft on mobility events management > (http://www.ietf.org/internet-drafts/draft-ietf-spirits-mobility-00.txt) > > Any other ideas? Any thoughts would be appreciated. > > Thanks, > > - vijay -- Vijay K. Gurbani vkg@{lucent.com,research.bell-labs.com,acm.org} Wireless Networks Group/Internet Software and Services Lucent Technologies/Bell Labs Innovations, 2000 Lucent Lane, Rm 6G-440 Naperville, Illinois 60566 Voice: +1 630 224 0216 _______________________________________________ SPIRITS mailing list SPIRITS@lists.bell-labs.com http://lists.bell-labs.com/mailman/listinfo/spirits _______________________________________________ SPIRITS mailing list SPIRITS@lists.bell-labs.com http://lists.bell-labs.com/mailman/listinfo/spirits From spirits-admin@lists.bell-labs.com Fri Feb 7 10:00:26 2003 Received: from share.research.bell-labs.com (share.research.bell-labs.com [204.178.16.58]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA12901 for ; Fri, 7 Feb 2003 10:00:25 -0500 (EST) Received: from share.research.bell-labs.com (localhost [127.0.0.1]) by share.research.bell-labs.com (8.11.6/8.11.6) with ESMTP id h17F41226811; Fri, 7 Feb 2003 10:04:01 -0500 Received: from dirty.research.bell-labs.com (ns1.research.bell-labs.com [204.178.16.6]) by share.research.bell-labs.com (8.11.6/8.11.6) with ESMTP id h17F37226798 for ; Fri, 7 Feb 2003 10:03:07 -0500 Received: from lists.bell-labs.com (H-135-104-27-211.research.bell-labs.com [135.104.27.211]) by dirty.research.bell-labs.com (8.12.5/8.12.5) with ESMTP id h17F2whN057636 for ; Fri, 7 Feb 2003 10:02:58 -0500 (EST) Received: by lists.bell-labs.com (Postfix) id 5ECED443A5; Fri, 7 Feb 2003 10:02:53 -0500 (EST) Delivered-To: spirits@sunny.research.bell-labs.com Received: from grubby.research.bell-labs.com (guard.research.bell-labs.com [135.104.2.9]) by lists.bell-labs.com (Postfix) with ESMTP id 25E2D443A4 for ; Fri, 7 Feb 2003 10:02:53 -0500 (EST) Received: from ih2mail.ih.lucent.com (ih2mail.ih.lucent.com [135.1.241.39]) by grubby.research.bell-labs.com (8.11.6/8.11.6) with ESMTP id h17F2lY70306 for ; Fri, 7 Feb 2003 10:02:48 -0500 (EST) Received: from lucent.com by ih2mail.ih.lucent.com (8.8.8+Sun/EMS-1.5 sol2) id JAA29502; Fri, 7 Feb 2003 09:02:43 -0600 (CST) Message-ID: <3E43CA75.2010406@lucent.com> From: "Vijay K. Gurbani" Organization: Lucent Technologies, Inc./Bell Laboratories 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: dmalhotra@hss.hns.com Cc: dmoreno@airtel.es, SPIRITS list Subject: Re: [SPIRITS] Representing non-call related events References: <65256CC4.00151330.00@sandesh.hss.hns.com> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Sender: spirits-admin@lists.bell-labs.com Errors-To: spirits-admin@lists.bell-labs.com X-BeenThere: spirits@lists.bell-labs.com X-Mailman-Version: 2.0.8 Precedence: bulk List-Help: List-Post: List-Subscribe: , List-Id: List-Unsubscribe: , List-Archive: Date: Fri, 07 Feb 2003 09:02:13 -0600 Content-Transfer-Encoding: 7bit dmalhotra@hss.hns.com wrote: > > Vijay, > Are you trying to define the way supplementary services shall work > in the SPIRITS model ? No; I think the word 'supplementary' in my email may have been mis-interpreted. I understand that 'supplementary' is a well defined term in the PSTN/ISDN/GSM domain. In SPIRITS, I want to be able to provide services based on network events that are not part of call setup, teardown, or maintenance. For instance, in the wireless network, mobility management events are of prime interest to us as a service enabler (some work has been done by Daniel Moreno in cataloging these for SPIRITS, see http://www.ietf.org/internet-drafts/draft-ietf-spirits-mobility-00.txt). But there are a lot of other events happening that we can exploit. For instance, a parent can subscribe to the event of a college bound offspring's pre-paid card balance falling below a certain limit in order to replenish the account (or rescind it, as the case may be). Not to mention my SMS->IM service. The question is how to represent a set of such events in an extensible manner without tying the SPIRITS protocol to a particular service instance. Bruno Chatras' email on this topic (which was CC'd to the list) helps as well; I need some time to understand the points he is making before posting a response... Thanks, - vijay -- Vijay K. Gurbani vkg@{lucent.com,research.bell-labs.com,acm.org} Wireless Networks Group/Internet Software and Services Lucent Technologies/Bell Labs Innovations, 2000 Lucent Lane, Rm 6G-440 Naperville, Illinois 60566 Voice: +1 630 224 0216 _______________________________________________ SPIRITS mailing list SPIRITS@lists.bell-labs.com http://lists.bell-labs.com/mailman/listinfo/spirits From spirits-admin@lists.bell-labs.com Mon Feb 10 10:04:28 2003 Received: from share.research.bell-labs.com (share.research.bell-labs.com [204.178.16.58]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA11449 for ; Mon, 10 Feb 2003 10:04:27 -0500 (EST) Received: from share.research.bell-labs.com (localhost [127.0.0.1]) by share.research.bell-labs.com (8.11.6/8.11.6) with ESMTP id h1AF81223206; Mon, 10 Feb 2003 10:08:01 -0500 Received: from dirty.research.bell-labs.com (ns1.research.bell-labs.com [204.178.16.6]) by share.research.bell-labs.com (8.11.6/8.11.6) with ESMTP id h1AF7C223192 for ; Mon, 10 Feb 2003 10:07:12 -0500 Received: from lists.bell-labs.com (H-135-104-27-211.research.bell-labs.com [135.104.27.211]) by dirty.research.bell-labs.com (8.12.5/8.12.5) with ESMTP id h1AF73hN087575 for ; Mon, 10 Feb 2003 10:07:03 -0500 (EST) Received: by lists.bell-labs.com (Postfix) id E3A79443A5; Mon, 10 Feb 2003 10:06:57 -0500 (EST) Delivered-To: spirits@sunny.research.bell-labs.com Received: from scummy.research.bell-labs.com (guard.research.bell-labs.com [135.104.2.10]) by lists.bell-labs.com (Postfix) with ESMTP id BDD2A443A4 for ; Mon, 10 Feb 2003 10:06:57 -0500 (EST) Received: from mvmail.mv.lucent.com (mvmail.mv.lucent.com [135.13.96.58]) by scummy.research.bell-labs.com (8.11.6/8.11.6) with ESMTP id h1AF6jI86466 for ; Mon, 10 Feb 2003 10:06:46 -0500 (EST) Received: from bell-labs.com (NJ7460FAYNBERG4.ho.lucent.com [135.17.52.154]) by mvmail.mv.lucent.com (8.8.8+Sun/EMS-1.5 sol2) id KAA12593; Mon, 10 Feb 2003 10:06:43 -0500 (EST) Message-ID: <3E47C003.2E50CF2F@bell-labs.com> From: Igor Faynberg Reply-To: faynberg@lucent.com Organization: Lucent Technologies X-Mailer: Mozilla 4.76 [en]C-CCK-MCD EMS-1.5 (Windows NT 5.0; U) X-Accept-Language: en MIME-Version: 1.0 To: "Vijay K. Gurbani" Cc: SPIRITS list Subject: Re: [SPIRITS] Representing non-call related events References: <3E3AF0CD.9020107@lucent.com> <3E3FFCF4.8050801@lucent.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: spirits-admin@lists.bell-labs.com Errors-To: spirits-admin@lists.bell-labs.com X-BeenThere: spirits@lists.bell-labs.com X-Mailman-Version: 2.0.8 Precedence: bulk List-Help: List-Post: List-Subscribe: , List-Id: List-Unsubscribe: , List-Archive: Date: Mon, 10 Feb 2003 10:06:43 -0500 Content-Transfer-Encoding: 7bit I don't think there is much useful for us in the CUSF specification, but all the information there is can be found in ITU-T Recommendations Q.1224 and Q.1228. Igor "Vijay K. Gurbani" wrote: > > Folks: > > Regarding the discussion below, it was suggested to me in a private > email that the CUSF functional entity of IN-CS2 be looked into. > > Is there anyone on the list familiar with this and willing to pitch > in some time? Any discussion (and help) will be extremely fruitful, I > think... > > Thanks, > > - vijay > > Vijay K. Gurbani wrote: > > Folks: > > > > I want to start a discussion about how to best represent non-call > > related events in the SPIRITS XML payload. > > > > Non-call related events include those concerned with mobility, > > location, SMS, etc. Note that no DP is involved here; in fact, > > SPIRITS has a Event token called 'spirits-user-prof' for these > > types of events. > > > > One way to represent these events to have a specific element > > called for such SUPplementary services. Thus, in order > > to transform a SMS into an IM, the SUBSCRIBE payload could > > conceivably contain: > > > > > > > > Notify > > 16302240216 > > > > > > However, that puts us in the dubious position of specifying all > > the possible supplementary services in SPIRITS -- which is > > definitely NOT what we want to do. One way to combat that problem > > is to say that the value of "app" attribute is a token, the details > > and semantics of which are dependent on the token. > > > > How do we handle location? Maybe we can scour geopriv for some > > answers (see > > http://www.ietf.org/internet-drafts/draft-daviel-html-geo-tag-05.txt) > > as well as Daniel Moreno's draft on mobility events management > > (http://www.ietf.org/internet-drafts/draft-ietf-spirits-mobility-00.txt) > > > > Any other ideas? Any thoughts would be appreciated. > > > > Thanks, > > > > - vijay > > -- > Vijay K. Gurbani vkg@{lucent.com,research.bell-labs.com,acm.org} > Wireless Networks Group/Internet Software and Services > Lucent Technologies/Bell Labs Innovations, 2000 Lucent Lane, Rm 6G-440 > Naperville, Illinois 60566 Voice: +1 630 224 0216 > > _______________________________________________ > SPIRITS mailing list > SPIRITS@lists.bell-labs.com > http://lists.bell-labs.com/mailman/listinfo/spirits _______________________________________________ SPIRITS mailing list SPIRITS@lists.bell-labs.com http://lists.bell-labs.com/mailman/listinfo/spirits From spirits-admin@lists.bell-labs.com Mon Feb 10 23:35:14 2003 Received: from share.research.bell-labs.com (share.research.bell-labs.com [204.178.16.58]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id XAA08223 for ; Mon, 10 Feb 2003 23:35:14 -0500 (EST) Received: from share.research.bell-labs.com (localhost [127.0.0.1]) by share.research.bell-labs.com (8.11.6/8.11.6) with ESMTP id h1B4d1227417; Mon, 10 Feb 2003 23:39:01 -0500 Received: from dirty.research.bell-labs.com (ns1.research.bell-labs.com [204.178.16.6]) by share.research.bell-labs.com (8.11.6/8.11.6) with ESMTP id h1B4cj227404 for ; Mon, 10 Feb 2003 23:38:45 -0500 Received: from lists.bell-labs.com (H-135-104-27-211.research.bell-labs.com [135.104.27.211]) by dirty.research.bell-labs.com (8.12.5/8.12.5) with ESMTP id h1B4cZhN094251 for ; Mon, 10 Feb 2003 23:38:35 -0500 (EST) Received: by lists.bell-labs.com (Postfix) id 99762443A5; Mon, 10 Feb 2003 23:38:30 -0500 (EST) Delivered-To: spirits@sunny.research.bell-labs.com Received: from scummy.research.bell-labs.com (guard.research.bell-labs.com [135.104.2.10]) by lists.bell-labs.com (Postfix) with ESMTP id 708CF443A4 for ; Mon, 10 Feb 2003 23:38:30 -0500 (EST) Received: from dusty.research.bell-labs.com (dusty.research.bell-labs.com [135.104.2.7]) by scummy.research.bell-labs.com (8.11.6/8.11.6) with ESMTP id h1B4cRI51728 for ; Mon, 10 Feb 2003 23:38:27 -0500 (EST) Received: from hindon.hss.co.in ([202.54.26.202]) by dusty.research.bell-labs.com (8.12.6/8.12.6) with ESMTP id h1B4ZHoJ020037 for ; Mon, 10 Feb 2003 23:35:18 -0500 (EST) Received: from hindon.hss.co.in (localhost [127.0.0.1]) by hindon.hss.co.in (8.10.0/8.10.0) with ESMTP id h1B4ajs11906 for ; Tue, 11 Feb 2003 10:06:45 +0530 (IST) Received: from ultra.hss.co.in (ultra.hss.hns.com [192.168.100.5]) by hindon.hss.co.in (8.10.0/8.10.0) with ESMTP id h1B4ai211902; Tue, 11 Feb 2003 10:06:44 +0530 (IST) Received: from sandesh.hss.hns.com (localhost [127.0.0.1]) by ultra.hss.co.in (8.10.0/8.10.0) with SMTP id h1B4d8S28274; Tue, 11 Feb 2003 10:09:08 +0530 (IST) Received: by sandesh.hss.hns.com(Lotus SMTP MTA v4.6.3 (733.2 10-16-1998)) id 65256CCA.0018C375 ; Tue, 11 Feb 2003 10:00:29 +0530 X-Lotus-FromDomain: HSS From: dmalhotra@hss.hns.com To: faynberg@lucent.com Cc: "Vijay K. Gurbani" , SPIRITS list Message-ID: <65256CCA.0018C245.00@sandesh.hss.hns.com> Subject: Re: [SPIRITS] Representing non-call related events Mime-Version: 1.0 Content-type: text/plain; charset=us-ascii Content-Disposition: inline Sender: spirits-admin@lists.bell-labs.com Errors-To: spirits-admin@lists.bell-labs.com X-BeenThere: spirits@lists.bell-labs.com X-Mailman-Version: 2.0.8 Precedence: bulk List-Help: List-Post: List-Subscribe: , List-Id: List-Unsubscribe: , List-Archive: Date: Tue, 11 Feb 2003 10:00:25 +0530 Hi Igor, The functionality is there to serve the same purpose only. Why to re-invent the wheel. If there is something lacking to serve the purpose, the intent can be enhance the existing functionalities. Regards Dhiraj Igor Faynberg on 02/10/2003 08:36:43 PM Please respond to faynberg@lucent.com To: "Vijay K. Gurbani" cc: SPIRITS list (bcc: Dhiraj Malhotra/HSS) Subject: Re: [SPIRITS] Representing non-call related events I don't think there is much useful for us in the CUSF specification, but all the information there is can be found in ITU-T Recommendations Q.1224 and Q.1228. Igor "Vijay K. Gurbani" wrote: > > Folks: > > Regarding the discussion below, it was suggested to me in a private > email that the CUSF functional entity of IN-CS2 be looked into. > > Is there anyone on the list familiar with this and willing to pitch > in some time? Any discussion (and help) will be extremely fruitful, I > think... > > Thanks, > > - vijay > > Vijay K. Gurbani wrote: > > Folks: > > > > I want to start a discussion about how to best represent non-call > > related events in the SPIRITS XML payload. > > > > Non-call related events include those concerned with mobility, > > location, SMS, etc. Note that no DP is involved here; in fact, > > SPIRITS has a Event token called 'spirits-user-prof' for these > > types of events. > > > > One way to represent these events to have a specific element > > called for such SUPplementary services. Thus, in order > > to transform a SMS into an IM, the SUBSCRIBE payload could > > conceivably contain: > > > > > > > > Notify > > 16302240216 > > > > > > However, that puts us in the dubious position of specifying all > > the possible supplementary services in SPIRITS -- which is > > definitely NOT what we want to do. One way to combat that problem > > is to say that the value of "app" attribute is a token, the details > > and semantics of which are dependent on the token. > > > > How do we handle location? Maybe we can scour geopriv for some > > answers (see > > http://www.ietf.org/internet-drafts/draft-daviel-html-geo-tag-05.txt) > > as well as Daniel Moreno's draft on mobility events management > > (http://www.ietf.org/internet-drafts/draft-ietf-spirits-mobility-00.txt) > > > > Any other ideas? Any thoughts would be appreciated. > > > > Thanks, > > > > - vijay > > -- > Vijay K. Gurbani vkg@{lucent.com,research.bell-labs.com,acm.org} > Wireless Networks Group/Internet Software and Services > Lucent Technologies/Bell Labs Innovations, 2000 Lucent Lane, Rm 6G-440 > Naperville, Illinois 60566 Voice: +1 630 224 0216 > > _______________________________________________ > SPIRITS mailing list > SPIRITS@lists.bell-labs.com > http://lists.bell-labs.com/mailman/listinfo/spirits _______________________________________________ SPIRITS mailing list SPIRITS@lists.bell-labs.com http://lists.bell-labs.com/mailman/listinfo/spirits _______________________________________________ SPIRITS mailing list SPIRITS@lists.bell-labs.com http://lists.bell-labs.com/mailman/listinfo/spirits From spirits-admin@lists.bell-labs.com Tue Feb 11 12:01:29 2003 Received: from share.research.bell-labs.com (share.research.bell-labs.com [204.178.16.58]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA11567 for ; Tue, 11 Feb 2003 12:01:28 -0500 (EST) Received: from share.research.bell-labs.com (localhost [127.0.0.1]) by share.research.bell-labs.com (8.11.6/8.11.6) with ESMTP id h1BH52231780; Tue, 11 Feb 2003 12:05:02 -0500 Received: from dirty.research.bell-labs.com (ns1.research.bell-labs.com [204.178.16.6]) by share.research.bell-labs.com (8.11.6/8.11.6) with ESMTP id h1BH4s231761 for ; Tue, 11 Feb 2003 12:04:54 -0500 Received: from lists.bell-labs.com (H-135-104-27-211.research.bell-labs.com [135.104.27.211]) by dirty.research.bell-labs.com (8.12.5/8.12.5) with ESMTP id h1BH4ihN000208 for ; Tue, 11 Feb 2003 12:04:44 -0500 (EST) Received: by lists.bell-labs.com (Postfix) id A3031443A5; Tue, 11 Feb 2003 12:04:39 -0500 (EST) Delivered-To: spirits@sunny.research.bell-labs.com Received: from scummy.research.bell-labs.com (guard.research.bell-labs.com [135.104.2.10]) by lists.bell-labs.com (Postfix) with ESMTP id 7A151443A4 for ; Tue, 11 Feb 2003 12:04:39 -0500 (EST) Received: from mvmail.mv.lucent.com (mvmail.mv.lucent.com [135.13.96.58]) by scummy.research.bell-labs.com (8.11.6/8.11.6) with ESMTP id h1BH4WI98336 for ; Tue, 11 Feb 2003 12:04:33 -0500 (EST) Received: from bell-labs.com (NJ7460FAYNBERG4.ho.lucent.com [135.17.52.154]) by mvmail.mv.lucent.com (8.8.8+Sun/EMS-1.5 sol2) id MAA13152; Tue, 11 Feb 2003 12:04:28 -0500 (EST) Message-ID: <3E492D19.BF7C4A13@bell-labs.com> From: Igor Faynberg Reply-To: faynberg@lucent.com Organization: Lucent Technologies X-Mailer: Mozilla 4.76 [en]C-CCK-MCD EMS-1.5 (Windows NT 5.0; U) X-Accept-Language: en MIME-Version: 1.0 To: dmalhotra@hss.hns.com Cc: faynberg@lucent.com, "Vijay K. Gurbani" , SPIRITS list Subject: Re: [SPIRITS] Representing non-call related events References: <65256CCA.0018C245.00@sandesh.hss.hns.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: spirits-admin@lists.bell-labs.com Errors-To: spirits-admin@lists.bell-labs.com X-BeenThere: spirits@lists.bell-labs.com X-Mailman-Version: 2.0.8 Precedence: bulk List-Help: List-Post: List-Subscribe: , List-Id: List-Unsubscribe: , List-Archive: Date: Tue, 11 Feb 2003 12:04:25 -0500 Content-Transfer-Encoding: 7bit Dhiraj, I agree. (By the way, my note was concerning CS-2, where not much except the definition was present. As Bruno suggested, we would need to look at CS-3, where indeed the CUSF DPs were defined.) Igor dmalhotra@hss.hns.com wrote: > > Hi Igor, > The functionality is there to serve the same purpose only. Why to > re-invent the wheel. If there is something lacking to serve the purpose, the > intent can be enhance the existing functionalities. > Regards > Dhiraj > > Igor Faynberg on 02/10/2003 08:36:43 PM > > Please respond to faynberg@lucent.com > > To: "Vijay K. Gurbani" > cc: SPIRITS list (bcc: Dhiraj Malhotra/HSS) > > Subject: Re: [SPIRITS] Representing non-call related events > > I don't think there is much useful for us in the CUSF specification, but all > the information there is can be found in ITU-T Recommendations Q.1224 and > Q.1228. > > Igor > > "Vijay K. Gurbani" wrote: > > > > Folks: > > > > Regarding the discussion below, it was suggested to me in a private > > email that the CUSF functional entity of IN-CS2 be looked into. > > > > Is there anyone on the list familiar with this and willing to pitch > > in some time? Any discussion (and help) will be extremely fruitful, I > > think... > > > > Thanks, > > > > - vijay > > > > Vijay K. Gurbani wrote: > > > Folks: > > > > > > I want to start a discussion about how to best represent non-call > > > related events in the SPIRITS XML payload. > > > > > > Non-call related events include those concerned with mobility, > > > location, SMS, etc. Note that no DP is involved here; in fact, > > > SPIRITS has a Event token called 'spirits-user-prof' for these > > > types of events. > > > > > > One way to represent these events to have a specific element > > > called for such SUPplementary services. Thus, in order > > > to transform a SMS into an IM, the SUBSCRIBE payload could > > > conceivably contain: > > > > > > > > > > > > Notify > > > 16302240216 > > > > > > > > > However, that puts us in the dubious position of specifying all > > > the possible supplementary services in SPIRITS -- which is > > > definitely NOT what we want to do. One way to combat that problem > > > is to say that the value of "app" attribute is a token, the details > > > and semantics of which are dependent on the token. > > > > > > How do we handle location? Maybe we can scour geopriv for some > > > answers (see > > > http://www.ietf.org/internet-drafts/draft-daviel-html-geo-tag-05.txt) > > > as well as Daniel Moreno's draft on mobility events management > > > (http://www.ietf.org/internet-drafts/draft-ietf-spirits-mobility-00.txt) > > > > > > Any other ideas? Any thoughts would be appreciated. > > > > > > Thanks, > > > > > > - vijay > > > > -- > > Vijay K. Gurbani vkg@{lucent.com,research.bell-labs.com,acm.org} > > Wireless Networks Group/Internet Software and Services > > Lucent Technologies/Bell Labs Innovations, 2000 Lucent Lane, Rm 6G-440 > > Naperville, Illinois 60566 Voice: +1 630 224 0216 > > > > _______________________________________________ > > SPIRITS mailing list > > SPIRITS@lists.bell-labs.com > > http://lists.bell-labs.com/mailman/listinfo/spirits > _______________________________________________ > SPIRITS mailing list > SPIRITS@lists.bell-labs.com > http://lists.bell-labs.com/mailman/listinfo/spirits _______________________________________________ SPIRITS mailing list SPIRITS@lists.bell-labs.com http://lists.bell-labs.com/mailman/listinfo/spirits From spirits-admin@lists.bell-labs.com Mon Feb 24 10:20:09 2003 Received: from share.research.bell-labs.com (share.research.bell-labs.com [204.178.16.58]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA16434 for ; Mon, 24 Feb 2003 10:20:09 -0500 (EST) Received: from share.research.bell-labs.com (localhost [127.0.0.1]) by share.research.bell-labs.com (8.11.6/8.11.6) with ESMTP id h1OFO2206677; Mon, 24 Feb 2003 10:24:02 -0500 Received: from dirty.research.bell-labs.com (ns1.research.bell-labs.com [204.178.16.6]) by share.research.bell-labs.com (8.11.6/8.11.6) with ESMTP id h1OFNI206664 for ; Mon, 24 Feb 2003 10:23:18 -0500 Received: from lists.bell-labs.com (H-135-104-27-211.research.bell-labs.com [135.104.27.211]) by dirty.research.bell-labs.com (8.12.5/8.12.5) with ESMTP id h1OFN7hN034040 for ; Mon, 24 Feb 2003 10:23:07 -0500 (EST) Received: by lists.bell-labs.com (Postfix) id 9E74A443A5; Mon, 24 Feb 2003 10:23:02 -0500 (EST) Delivered-To: spirits@sunny.research.bell-labs.com Received: from scummy.research.bell-labs.com (guard.research.bell-labs.com [135.104.2.10]) by lists.bell-labs.com (Postfix) with ESMTP id 74589443A4 for ; Mon, 24 Feb 2003 10:23:02 -0500 (EST) Received: from ih2mail.ih.lucent.com (ih2mail.ih.lucent.com [135.1.241.39]) by scummy.research.bell-labs.com (8.11.6/8.11.6) with ESMTP id h1OFMrI99781 for ; Mon, 24 Feb 2003 10:22:53 -0500 (EST) Received: from lucent.com by ih2mail.ih.lucent.com (8.8.8+Sun/EMS-1.5 sol2) id JAA09332; Mon, 24 Feb 2003 09:22:51 -0600 (CST) Message-ID: <3E5A388B.4080506@lucent.com> From: "Vijay K. Gurbani" Organization: Lucent Technologies, Inc./Bell Laboratories 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: SPIRITS list Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Subject: [SPIRITS] I-D on SPIRITS implementations Sender: spirits-admin@lists.bell-labs.com Errors-To: spirits-admin@lists.bell-labs.com X-BeenThere: spirits@lists.bell-labs.com X-Mailman-Version: 2.0.8 Precedence: bulk List-Help: List-Post: List-Subscribe: , List-Id: List-Unsubscribe: , List-Archive: Date: Mon, 24 Feb 2003 09:21:47 -0600 Content-Transfer-Encoding: 7bit Folks: I have submitted an I-D to the SPIRITS WG on an early implementation of SPIRITS. It is available at: http://www.ietf.org/internet-drafts/draft-gurbani-spirits-implementation-00.txt Thanks, - vijay -- Vijay K. Gurbani vkg@{lucent.com,research.bell-labs.com,acm.org} Wireless Networks Group/Internet Software and Services Lucent Technologies/Bell Labs Innovations, 2000 Lucent Lane, Rm 6G-440 Naperville, Illinois 60566 Voice: +1 630 224 0216 _______________________________________________ SPIRITS mailing list SPIRITS@lists.bell-labs.com http://lists.bell-labs.com/mailman/listinfo/spirits