From extest-admin@lists.bell-labs.com Sat Mar 1 05:17:31 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 FAA02438 for ; Sat, 1 Mar 2003 05:17:31 -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 h21AJg228611 for ; Sat, 1 Mar 2003 05:19:42 -0500 Date: Sat, 1 Mar 2003 05:19:42 -0500 Message-Id: <200303011019.h21AJg228611@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 Mar 11 17:11:03 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 RAA14721 for ; Tue, 11 Mar 2003 17:11:03 -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 h2BMD2116884; Tue, 11 Mar 2003 17:13:02 -0500 Received: from crufty.research.bell-labs.com (ns2.research.bell-labs.com [204.178.16.49]) by share.research.bell-labs.com (8.11.6/8.11.6) with ESMTP id h2BMC5116871 for ; Tue, 11 Mar 2003 17:12:05 -0500 Received: from lists.bell-labs.com (H-135-104-27-211.research.bell-labs.com [135.104.27.211]) by crufty.research.bell-labs.com (8.12.8/8.12.8) with ESMTP id h2BMBrkH054321 for ; Tue, 11 Mar 2003 17:11:53 -0500 (EST) Received: by lists.bell-labs.com (Postfix) id 6BC82443A5; Tue, 11 Mar 2003 17:11:48 -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 43AA2443A4 for ; Tue, 11 Mar 2003 17:11:48 -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.12.8/8.12.8) with ESMTP id h2BMBkpi013604 for ; Tue, 11 Mar 2003 17:11:46 -0500 (EST) Received: from pop-2.dnv.wideopenwest.com (gtwy.nap.wideopenwest.com [64.233.207.11] (may be forged)) by dusty.research.bell-labs.com (8.12.8/8.12.8) with ESMTP id h2BMArUo008097 for ; Tue, 11 Mar 2003 17:10:53 -0500 (EST) Received: from ieee.org (d233-144-198.nap.wideopenwest.com [64.233.198.144]) by pop-2.dnv.wideopenwest.com (8.11.6/8.11.6) with ESMTP id h2BMH5V26622; Tue, 11 Mar 2003 16:17:05 -0600 Message-ID: <3E6E5F32.4060301@ieee.org> From: Alec Brusilovsky User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.0.2) Gecko/20021120 Netscape/7.01 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] Agenda (proposed) for the March 18 session in SF 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 Mar 2003 16:12:02 -0600 Content-Transfer-Encoding: 7bit Ladies and Gentlemen, We have a few quite interesting I-Ds on SPIRITS Protocol, IS-41, CAMEL and our first SPIRITS Implementation. Issues from these I-ds are to be discussed at our upcoming meeting. Our own Agenda@ietf.org (thanks, Dinara!) has kindly scheduled SPIRITS session in San Francisco for Tuesday, March 18th. at 1-2 p.m. The proposed Agenda for the meeting is attached below. 1. Goals of the session - Alec Brusilovsky - 3 min. 2. Agenda bashing - General Discussion - 2 min. 3. Issues from the mail exploder regarding the SPIRITS Protocol I-D - General Discussion - 15 min. - subscribing to multiple DPs; - representing non-call related events Source: http://www.ietf.org/internet-drafts/draft-ietf-spirits-protocol-04.txt 4. SPIRITS Protocol Security - General Discussion - 10 min Source: http://www.ietf.org/internet-drafts/draft-ietf-spirits-security-00.txt 5. SPIRITS and mobility issues - General Discussion - 10 min. Sources: http://www.ietf.org/internet-drafts/draft-ietf-spirits-mobility-01.txt http://www.ietf.org/internet-drafts/draft-brusilovsky-spirits-is41-00.txt 6. SPIRITS Implementation - General Discussion - 15 min. Source: http://www.ietf.org/internet-drafts/draft-gurbani-spirits-implementation-00.txt 6. Conclusions - General discussion - 5 min. Please sound your additions/changes/concerns here on the mailing list and/or during the Agenda Bashing time at the session. Kind regards, Alec -- Alec Brusilovsky abrusilovsky@ieee.org Naperville, IL USA +1.630.369.8196 _______________________________________________ SPIRITS mailing list SPIRITS@lists.bell-labs.com http://lists.bell-labs.com/mailman/listinfo/spirits From spirits-admin@lists.bell-labs.com Wed Mar 19 17:32:57 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 RAA12649 for ; Wed, 19 Mar 2003 17:32:57 -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 h2JMZ2102252; Wed, 19 Mar 2003 17:35: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 h2JMY7102233 for ; Wed, 19 Mar 2003 17:34: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.8/8.12.8) with ESMTP id h2JMXsN5082907 for ; Wed, 19 Mar 2003 17:33:54 -0500 (EST) Received: by lists.bell-labs.com (Postfix) id 420B8443A5; Wed, 19 Mar 2003 17:33:49 -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 1FAA9443A4 for ; Wed, 19 Mar 2003 17:33:49 -0500 (EST) Received: from ih2mail.ih.lucent.com (ih2mail.ih.lucent.com [135.1.241.39]) by scummy.research.bell-labs.com (8.12.8/8.12.8) with ESMTP id h2JMXljt024587 for ; Wed, 19 Mar 2003 17:33:47 -0500 (EST) Received: from lucent.com by ih2mail.ih.lucent.com (8.8.8+Sun/EMS-1.5 sol2) id QAA23724; Wed, 19 Mar 2003 16:33:46 -0600 (CST) Message-ID: <3E78F049.3060605@lucent.com> From: "Vijay K. Gurbani" User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.0.0) Gecko/20020530 X-Accept-Language: en-us, en MIME-Version: 1.0 To: spirits@lists.bell-labs.com Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Subject: [SPIRITS] Redirection in SPIRITS 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, 19 Mar 2003 16:33:45 -0600 Content-Transfer-Encoding: 7bit Folks: One issue that has come up in conjunction to the services enabled by SPIRITS is how to best do redirection. For instance, an application server may subscribe to the equivalent of a Terminating Attempt Authorized trigger (or Terminating Busy trigger) to perform redirection services. How do we realize such services in SPIRITS? So far, using ICW as a canonical example, the PSTN sends an INVITE and expect a 3xx response redirecting it to alternative destinations. However, given the advent of events in the SIP WG, there is a better way to do these types of services which does not require the heavy-weight processing of the INVITE transaction. And that is the use of "message/sipfrag" MIME type (http://www.ietf.org/rfc/rfc3420.txt). Using this, the 200 OK (NOTIFY) from the application server (which is a SPIRITS server as well), instead of containing an empty body, will instead contain a body of MIME type "message/sipfrag". The body will include fragments of a 3xx final response, including the Contacts to redirect the call to. Here is a sample call flow: PSTN App Server |<-------------------+ SUBS (body: application/spirits-event) +------------------->| 200 OK ... ... +------------------->| NOT (body: application/spirits-event) |<-------------------+ 200 OK (body: message/sipfrag) Of course, this does not deprecate or obsolete the use of an INVITE request; but rather it is yet another (light-weight) way to do redirection services in SIP. Comments/questions/opinions welcome. Regards, - 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 Fri Mar 21 01:07:57 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 BAA22937 for ; Fri, 21 Mar 2003 01:07:57 -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 h2L692114169; Fri, 21 Mar 2003 01:09: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 h2L68Q114156 for ; Fri, 21 Mar 2003 01:08:26 -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.8/8.12.8) with ESMTP id h2L68DN5097065 for ; Fri, 21 Mar 2003 01:08:13 -0500 (EST) Received: by lists.bell-labs.com (Postfix) id 43E27443A5; Fri, 21 Mar 2003 01:08:08 -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 1B4FA443A4 for ; Fri, 21 Mar 2003 01:08:08 -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.12.8/8.12.8) with ESMTP id h2L686jt049239 for ; Fri, 21 Mar 2003 01:08:06 -0500 (EST) Received: from hindon.hss.co.in (hindon.hss.co.in [202.54.26.202]) by dusty.research.bell-labs.com (8.12.8/8.12.8) with ESMTP id h2L66fUo004982 for ; Fri, 21 Mar 2003 01:06:43 -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 h2L65vs18587 for ; Fri, 21 Mar 2003 11:35:57 +0530 (IST) Received: from ultra.hss.co.in (ultra [192.168.100.5]) by hindon.hss.co.in (8.10.0/8.10.0) with ESMTP id h2L65r218573 for ; Fri, 21 Mar 2003 11:35:57 +0530 (IST) Received: from dlfmail1.hss.hns.com (localhost [127.0.0.1]) by ultra.hss.co.in (8.10.0/8.10.0) with SMTP id h2L68Y415340 for ; Fri, 21 Mar 2003 11:38:39 +0530 (IST) Received: by dlfmail1.hss.hns.com(Lotus SMTP MTA v4.6.5 (863.2 5-20-1999)) id 65256CF0.002068CC ; Fri, 21 Mar 2003 11:23:59 +0530 X-Lotus-FromDomain: HSS From: ucbabu@hss.hns.com To: spirits@lists.bell-labs.com Message-ID: <65256CF0.002067FA.00@dlfmail1.hss.hns.com> Mime-Version: 1.0 Content-type: text/plain; charset=us-ascii Content-Disposition: inline Subject: [SPIRITS] Re: SPIRITS digest, Vol 1 #64 - 1 msg 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, 21 Mar 2003 11:32:33 +0530 hi folks, If the User needs only the Redirection Service and wants to know about the Incoming Call, then in the "Subscribe" Message itself can specify the details of the redirection. Then if a call is ended to the user, then he will just be informed through the "Notify" message and the Call is redirected. But in this case he has no choice, other than the call being redirected. In this case the Service is much much lighter too. Do I make any sense? Talking about the INVITE and NOTIFY, definetly both the messages can be used to invoke a service at the Application Server. thanks UCB spirits-request@lists.bell-labs.com on 03/20/2003 10:31:08 PM Please respond to spirits@lists.bell-labs.com To: spirits@lists.bell-labs.com cc: (bcc: Uppen Babu Chava/HSS) Subject: SPIRITS digest, Vol 1 #64 - 1 msg Send SPIRITS mailing list submissions to spirits@lists.bell-labs.com To subscribe or unsubscribe via the World Wide Web, visit http://lists.bell-labs.com/mailman/listinfo/spirits or, via email, send a message with subject or body 'help' to spirits-request@lists.bell-labs.com You can reach the person managing the list at spirits-admin@lists.bell-labs.com When replying, please edit your Subject line so it is more specific than "Re: Contents of SPIRITS digest..." Today's Topics: 1. Redirection in SPIRITS (Vijay K. Gurbani) Message: 1 Delivered-To: spirits@sunny.research.bell-labs.com Message-ID: <3E78F049.3060605@lucent.com> Date: Wed, 19 Mar 2003 16:33:45 -0600 From: "Vijay K. Gurbani" User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.0.0) Gecko/20020530 MIME-Version: 1.0 To: spirits@lists.bell-labs.com Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Subject: [SPIRITS] Redirection in SPIRITS Sender: spirits-admin@lists.bell-labs.com Precedence: bulk List-Help: List-Post: List-Subscribe: , < mailto:spirits-request@lists.bell-labs.com?subject=subscribe> List-Id: List-Unsubscribe: , < mailto:spirits-request@lists.bell-labs.com?subject=unsubscribe> List-Archive: Folks: One issue that has come up in conjunction to the services enabled by SPIRITS is how to best do redirection. For instance, an application server may subscribe to the equivalent of a Terminating Attempt Authorized trigger (or Terminating Busy trigger) to perform redirection services. How do we realize such services in SPIRITS? So far, using ICW as a canonical example, the PSTN sends an INVITE and expect a 3xx response redirecting it to alternative destinations. However, given the advent of events in the SIP WG, there is a better way to do these types of services which does not require the heavy-weight processing of the INVITE transaction. And that is the use of "message/sipfrag" MIME type (http://www.ietf.org/rfc/rfc3420.txt). Using this, the 200 OK (NOTIFY) from the application server (which is a SPIRITS server as well), instead of containing an empty body, will instead contain a body of MIME type "message/sipfrag". The body will include fragments of a 3xx final response, including the Contacts to redirect the call to. Here is a sample call flow: PSTN App Server |<-------------------+ SUBS (body: application/spirits-event) +------------------->| 200 OK ... ... +------------------->| NOT (body: application/spirits-event) |<-------------------+ 200 OK (body: message/sipfrag) Of course, this does not deprecate or obsolete the use of an INVITE request; but rather it is yet another (light-weight) way to do redirection services in SIP. Comments/questions/opinions welcome. Regards, - 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 Mar 24 11:00:43 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 LAA24024 for ; Mon, 24 Mar 2003 11:00:43 -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 h2OG31122176; Mon, 24 Mar 2003 11:03:01 -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 h2OG2w122163 for ; Mon, 24 Mar 2003 11:02:58 -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.8/8.12.8) with ESMTP id h2OG2jN5028968 for ; Mon, 24 Mar 2003 11:02:45 -0500 (EST) Received: by lists.bell-labs.com (Postfix) id 73703443A5; Mon, 24 Mar 2003 11:02:40 -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 4D3CF443A4 for ; Mon, 24 Mar 2003 11:02:40 -0500 (EST) Received: from ih2mail.ih.lucent.com (ih2mail.ih.lucent.com [135.1.241.39]) by scummy.research.bell-labs.com (8.12.8/8.12.8) with ESMTP id h2OG2cjt099103 for ; Mon, 24 Mar 2003 11:02:39 -0500 (EST) Received: from lucent.com by ih2mail.ih.lucent.com (8.8.8+Sun/EMS-1.5 sol2) id KAA14522; Mon, 24 Mar 2003 10:02:34 -0600 (CST) Message-ID: <3E7F2C1C.1010609@lucent.com> From: "Vijay K. Gurbani" User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.0.0) Gecko/20020530 X-Accept-Language: en-us, en MIME-Version: 1.0 To: ucbabu@hss.hns.com Cc: spirits@lists.bell-labs.com Subject: Re: [SPIRITS] Re: SPIRITS digest, Vol 1 #64 - 1 msg References: <65256CF0.002067FA.00@dlfmail1.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: Mon, 24 Mar 2003 10:02:36 -0600 Content-Transfer-Encoding: 7bit ucbabu@hss.hns.com wrote: > > hi folks, > > If the User needs only the Redirection Service and wants to know about the > Incoming Call, then in the "Subscribe" Message itself can specify the > details of the redirection. One thing we do NOT want to do in SPIRITS is to outline specific services. We do want to *enable* services. To that extent, having the SUBSCRIBE specify details of the redirection would be attempting to specify the service. On the other hand, if SUBSCRIBE conatined the normal payload -- events to be monitored -- then the framework remains general enough and the specific redirection service is realized as outlined in my original email. > Talking about the INVITE and NOTIFY, definetly both the messages can be used > to invoke a service at the Application Server. Exactly; using the mechanism I proposed does not invalidate the use of INVITE. Regards, - 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