From extest-admin@lists.bell-labs.com Fri Mar 1 05:12:49 2002 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 FAA04239 for ; Fri, 1 Mar 2002 05:12:49 -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 g21ACpM00883 for ; Fri, 1 Mar 2002 05:12:51 -0500 Date: Fri, 1 Mar 2002 05:12:51 -0500 Message-Id: <200203011012.g21ACpM00883@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 5 10:22:23 2002 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 KAA04270 for ; Tue, 5 Mar 2002 10:22:23 -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 g25FM1M09742; Tue, 5 Mar 2002 10:22:01 -0500 Received: from crufty.research.bell-labs.com (crufty.research.bell-labs.com [204.178.16.49]) by share.research.bell-labs.com (8.11.6/8.11.6) with SMTP id g25FLsM09729 for ; Tue, 5 Mar 2002 10:21:54 -0500 Received: from lists.bell-labs.com ([135.104.27.211]) by crufty; Tue Mar 5 10:21:25 EST 2002 Received: by lists.bell-labs.com (Postfix) id 5AE894439E; Tue, 5 Mar 2002 10:21:18 -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 2A1DB4439D for ; Tue, 5 Mar 2002 10:21:18 -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 g25FLGk97847 for ; Tue, 5 Mar 2002 10:21:16 -0500 (EST) Received: from lucent.com by ih2mail.ih.lucent.com (8.8.8+Sun/EMS-1.5 sol2) id JAA02704; Tue, 5 Mar 2002 09:21:12 -0600 (CST) Message-ID: <3C84E260.A16069CB@lucent.com> From: Vijay Gurbani Organization: Lucent Technologies/Bell Laboratories X-Mailer: Mozilla 4.73 [en]C-CCK-MCD EMS-1.4 (Windows NT 5.0; U) X-Accept-Language: en MIME-Version: 1.0 To: spirits@lists.bell-labs.com Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Subject: [SPIRITS] Template-package issues for I-D 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, 05 Mar 2002 09:21:04 -0600 Content-Transfer-Encoding: 7bit Folks: Some private email exchange between myself and Adam Roach regarding the use of template-packages in the I-D for the SPIRITS protocol -- http://search.ietf.org/internet-drafts/draft-gurbani-spirits-protocol-01.txt For subsequent discussions and any resolutions, I would like to move it to the SPIRITS WG list. Comments on the I-D itself as well as the specific point discussed in the portion reproduced below are welcome. > Adam Roach wrote: > [...] > >>Your new draft still contains the misunderstanding that I was >>attempting to dispel in my previous node. To be clearer, I will >>quote a section from draft-ietf-sip-events-04: >> >> Event template-packages must be defined so that they can be >> applied to any arbitrary package. In other words, event >> template-packages cannot be specifically tied to one or a few >> "parent" packages in such a way that they will not work with >> other packages. >> >>In other words, if you define a template-package called "INDPs," >>it must make sense to refer to "presence.INDPs" and even >>"spirits.INDPs.INDPs". For the two "template-packages" your >>draft attempts to define, this simply isn't the case. >> > > Adam: > > I did read this in draft-ietf-sip-events-04. However, not remembering > the genesis of this requirement, I fail to understand its imposition (I > know last call for draft-ietf-sip-events-04 is over). That is not to say > that we will not adhere to it, but what function does it serve? After > all, events for a package X are germaine to the package X, and to any of > its sub-packages (or template-packages) only. > > Even in C++, a template class for matrix multiplication can be applied to > different types; however, the same template class cannot be used to > implement, say, a linked list of different types. > > It appears to me that template-packages definitely make sense within the > context of a package. However, to require a template-package to work > with *all* the packages in the universe is a bit too restrictive, IMHO. > > Please understand that I am not attempting to be difficult, just that I > am trying to understand the reasoning behind the requirement so I can > better > reflect it in our I-D. > > Thanks, > > - vijay Regards, - vijay -- Vijay K. Gurbani vkg@{lucent.com,research.bell-labs.com,acm.org} Internet Software and eServices Group Lucent Technologies/Bell Labs Innovations, 2000 Lucent Lane, Rm 6G-440 Naperville, Illinois 60566 Voice: +1 630 224 0216 Fax: +1 630 713 0184 _______________________________________________ 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 6 17:26:19 2002 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 RAA11247 for ; Wed, 6 Mar 2002 17:26:18 -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 g26MQ1M18230; Wed, 6 Mar 2002 17:26:01 -0500 Received: from crufty.research.bell-labs.com (crufty.research.bell-labs.com [204.178.16.49]) by share.research.bell-labs.com (8.11.6/8.11.6) with SMTP id g26MPsM18217 for ; Wed, 6 Mar 2002 17:25:54 -0500 Received: from lists.bell-labs.com ([135.104.27.211]) by crufty; Wed Mar 6 17:25:21 EST 2002 Received: by lists.bell-labs.com (Postfix) id 140344439E; Wed, 6 Mar 2002 17:25:13 -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 DD0464439D for ; Wed, 6 Mar 2002 17:25:12 -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 g26MPBo34269 for ; Wed, 6 Mar 2002 17:25:11 -0500 (EST) Received: from lucent.com by ih2mail.ih.lucent.com (8.8.8+Sun/EMS-1.5 sol2) id QAA24661; Wed, 6 Mar 2002 16:25:10 -0600 (CST) Message-ID: <3C869733.7060001@lucent.com> From: Alec Brusilovsky Organization: Lucent Technologies User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:0.9.4) Gecko/20011128 Netscape6/6.2.1 X-Accept-Language: en,ru,uk MIME-Version: 1.0 To: SPIRITS list Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Subject: [SPIRITS] Issues for the 3/19/02 meeting 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, 06 Mar 2002 16:24:51 -0600 Content-Transfer-Encoding: 7bit Ladies and Gentlemen, The following three I-D's are published and available from the IETF repository: 1. SPIRITS Protocol Requirements http://www.ietf.org/internet-drafts/draft-ietf-spirits-reqs-04.txt This is our new IESG approved Informational RFC. The status of this document in the RFC Editor queue RFC as of yesterday is: "EDIT = approved by IESG, awaiting processing and publishing" 2. Toward the Definition of the SIP Events Package for SPIRITS Protocol http://www.ietf.org/internet-drafts/draft-ietf-spirits-sip-evt-package-02.txt This I-D was discussed at the SLC meeting in December. This current version has all the issues raised at the SLC meeting resolved. 3. The SPIRITS Protocol http://www.ietf.org/internet-drafts/draft-gurbani-spirits-protocol-01.txt This I-D is a union of: SIP Event Package I-D, , IN Parameters I-D, , and Internet Caller-ID delivery example SPIRITS message flow. This is our first attempt to describe and define SPIRITS protocol, according to the architecture in RFC 3136 and requirements in draft-ietf-spirits-reqs-04.txt, current Informational RFC Candidate Issues for the 3/19 meeting: 1. v.01 of the SPIRITS Protocol I-D has absorbed the SIP Event Package for SPIRITS I-D. In the interest of speeding up the process of the SPIRITS Protocol definition, it might be necessary to have Event Package I-D and Protocol I-D developed separately. These I-Ds are then to be merged into a single Protocol I-D prior to its submission to the IESG. 2. The issue of using XML Schema instead of DTDs was discussed at he last meeting. So far, no work there has been done. 3. A list of the values of the parameters associated with the Event detection point to be carried in the SUBSCRIBE body. We need to define DTDs or Shema for these parameter lists. 4. MIME type: do we need a new MIME type (application/spirits-events) or does an existing one suffice? 5. IANA Issues. Do we need to register anything else, besides mime types:application/spirits-event, tokens: spirits.INDPs, spirits.user-prof]? 6. Security Considerations. Need to expand and address SPIRITS specific threats, i.e. SUBSCRIBE and/or NOTIFY spoofing. Any other issues for the 3/19 meeting? Kind regards, Alec _______________________________________________ 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 6 18:16:17 2002 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 SAA14357 for ; Wed, 6 Mar 2002 18:16:17 -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 g26NG1M18616; Wed, 6 Mar 2002 18:16:01 -0500 Received: from crufty.research.bell-labs.com (crufty.research.bell-labs.com [204.178.16.49]) by share.research.bell-labs.com (8.11.6/8.11.6) with SMTP id g26NFsM18603 for ; Wed, 6 Mar 2002 18:15:54 -0500 Received: from lists.bell-labs.com ([135.104.27.211]) by crufty; Wed Mar 6 18:14:45 EST 2002 Received: by lists.bell-labs.com (Postfix) id 8DA624439E; Wed, 6 Mar 2002 18:14:37 -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 5D4A14439D for ; Wed, 6 Mar 2002 18:14:37 -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 g26NEVo38130 for ; Wed, 6 Mar 2002 18:14:31 -0500 (EST) Received: from lucent.com by ih2mail.ih.lucent.com (8.8.8+Sun/EMS-1.5 sol2) id RAA17595; Wed, 6 Mar 2002 17:14:29 -0600 (CST) Message-ID: <3C86A2D2.9010009@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:0.9.4) Gecko/20011128 Netscape6/6.2.1 X-Accept-Language: en-us MIME-Version: 1.0 To: Alec Brusilovsky Cc: SPIRITS list Subject: Re: [SPIRITS] Issues for the 3/19/02 meeting References: <3C869733.7060001@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: Wed, 06 Mar 2002 17:14:26 -0600 Content-Transfer-Encoding: 7bit Alec Brusilovsky wrote: > Ladies and Gentlemen, > > The following three I-D's are published and available from the IETF > repository: > Issues for the 3/19 meeting: [...] > 1. v.01 of the SPIRITS Protocol I-D has absorbed the SIP Event Package > for SPIRITS I-D. In the interest of speeding up the process of the > SPIRITS Protocol definition, it might be necessary to have Event Package > I-D and Protocol I-D developed separately. These I-Ds are then to be > merged into a single Protocol I-D prior to its submission to the IESG. > > 2. The issue of using XML Schema instead of DTDs was discussed at he > last meeting. So far, no work there has been done. > > 3. A list of the values of the parameters associated with the Event > detection point to be carried in the SUBSCRIBE body. We need to define > DTDs or Shema for these parameter lists. Also, don't forget the NOTIFY bodies as well; these will contain the information that results when the subscribed event occurred. The information has to be carried back to the subscriber in some format. As it stands right now, in the I-D http://www.ietf.org/internet-drafts/draft-gurbani-spirits-protocol-01.txt we do list the INAP parameters for the DPs in Appendices A and B. Do we codify these DTDs in the RFC or leave them open-ended? The overall issue in (3) is very important and will probably benefit from some interaction at the Minneapolis IETF. > 4. MIME type: do we need a new MIME type (application/spirits-events) or > does an existing one suffice? > > 5. IANA Issues. Do we need to register anything else, besides mime > types:application/spirits-event, tokens: spirits.INDPs, spirits.user-prof]? This kind of ties into the email I posted a couple of days ago to the list -- the email between myself and Adam Roach. The gist of the email was that SPIRITS should have 2 packages and no template packages; i.e. spirits-INDPs and spirits-user-prof would be the two packages instead of spirits.INDPs and spirits.user-prof (INDPs and user-prof being a template-package of the "spirits" package). I am still struggling to make sense of this (I had initially envisioned user-prof and INDPs as a template-package of the "spirits" package -- Adam indicated that this is not the correct usage of template packages). Probably worth some time at the Minneapolis IETF. > 6. Security Considerations. Need to expand and address SPIRITS specific > threats, i.e. SUBSCRIBE and/or NOTIFY spoofing. I think that we can leverage the security mechanisms developed for SIP in the SIP WG for most of our work (augmented by Section 6 of the -05 SIP Events I-D) . Of more interest will be the interface that straddles the PSTN and the Internet... > Any other issues for the 3/19 meeting? Not right now; I am sure something else will strike me later... Thanks, - vijay -- Vijay K. Gurbani vkg@{lucent.com,research.bell-labs.com,acm.org} Internet Software and eServices Group Lucent Technologies/Bell Labs Innovations, 2000 Lucent Lane, Rm 6G-440 Naperville, Illinois 60566 Voice: +1 630 224 0216 Fax: +1 630 713 0184 _______________________________________________ SPIRITS mailing list SPIRITS@lists.bell-labs.com http://lists.bell-labs.com/mailman/listinfo/spirits From spirits-admin@lists.bell-labs.com Tue Mar 12 12:46:43 2002 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 MAA28758 for ; Tue, 12 Mar 2002 12:46: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 g2CHk6M25227; Tue, 12 Mar 2002 12:46:06 -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 SMTP id g2CHjiM25214 for ; Tue, 12 Mar 2002 12:45:44 -0500 Received: from lists.bell-labs.com ([135.104.27.211]) by dirty; Tue Mar 12 12:44:41 EST 2002 Received: by lists.bell-labs.com (Postfix) id F3D8C4439E; Tue, 12 Mar 2002 12:44:24 -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 CAEFC4439D for ; Tue, 12 Mar 2002 12:44:23 -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 g2CHiMo42070 for ; Tue, 12 Mar 2002 12:44:22 -0500 (EST) Received: from lucent.com by ih2mail.ih.lucent.com (8.8.8+Sun/EMS-1.5 sol2) id LAA07550; Tue, 12 Mar 2002 11:44:21 -0600 (CST) Message-ID: <3C8E3E62.6040009@lucent.com> From: Alec Brusilovsky Organization: Lucent Technologies User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:0.9.4) Gecko/20011128 Netscape6/6.2.1 X-Accept-Language: en,ru,uk MIME-Version: 1.0 To: SPIRITS list Cc: Steve Bellovin Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Subject: [SPIRITS] Minneapolis meeting agenda 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, 12 Mar 2002 11:44:02 -0600 Content-Transfer-Encoding: 7bit Ladies and Gentlemen, Our next meeting will be in Minneapolis on Tuesday, March 19, 2002 at 13:00. SPIRITS WG meeting Agenda 1. Agenda bashing - Chairs - 5 min. 2. ICIDD service in SPIRITS - example call flows and issues - V. Gurbani - 5 minutes 3. SPIRITS Protocol Issues - discussion - 45 minutes: a. v.01 of the SPIRITS Protocol I-D has absorbed the SIP Event Package for SPIRITS I-D. In the interest of speeding up the process of the SPIRITS Protocol definition, it might be necessary to have Event Package I-D and Protocol I-D developed separately. These I-Ds are then to be merged into a single Protocol I-D prior to its submission to the IESG. b. The issue of using XML Schema instead of DTDs was discussed at he last meeting. So far, no work there has been done. c. A list of the values of the parameters associated with the Event detection point to be carried in the SUBSCRIBE body. We need to define DTDs or Schema for these parameter lists. d. MIME type: do we need a new MIME type (application/spirits-events) or does an existing one suffice? e. IANA Issues. Do we need to register anything else, besides mime types: application/spirits-event, tokens: spirits.INDPs, spirits.user-prof]? Should SPIRITS have 2 packages and no template packages? I.e. spirits-INDPs and spirits-user-prof would be the two packages instead of spirits.INDPs and spirits.user-prof (INDPs and user-prof being a template-package of the "spirits" package). f. Security Considerations. Need to expand and address SPIRITS specific threats, i.e. SUBSCRIBE and/or NOTIFY spoofing. Can SPIRITS leverage the security mechanisms developed for SIP in the SIP WG for most of our work (augmented by Section 6 of the -05 SIP Events I-D)? 4. Conclusions - Chairs - 5 min. Background information for the meeting The following three I-D's are published and available from the IETF repository: 1. SPIRITS Protocol Requirements http://www.ietf.org/internet-drafts/draft-ietf-spirits-reqs-04.txt This is our new IESG approved Informational RFC. The status of this document in the RFC Editor queue RFC as of 3/5/02 is: "EDIT = approved by IESG, awaiting processing and publishing" 2. Toward the Definition of the SIP Events Package for SPIRITS Protocol http://www.ietf.org/internet-drafts/draft-ietf-spirits-sip-evt-package-02.txt This I-D was discussed at the SLC meeting in December. This current version has all the issues raised at the SLC meeting resolved. 3. The SPIRITS Protocol http://www.ietf.org/internet-drafts/draft-gurbani-spirits-protocol-01.txt This I-D is a union of: SIP Event Package I-D, , IN Parameters I-D, , and Internet Caller-ID delivery example SPIRITS message flow. This is our first attempt to describe and define SPIRITS protocol, according to the architecture in RFC 3136 and requirements in draft-ietf-spirits-reqs-04.txt, current Informational RFC Candidate No other burning issues were flashed on this list so far. See you all in Minneapolis! Kind regards, Alec _______________________________________________ SPIRITS mailing list SPIRITS@lists.bell-labs.com http://lists.bell-labs.com/mailman/listinfo/spirits From spirits-admin@lists.bell-labs.com Sun Mar 17 10:32:07 2002 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 KAA02711 for ; Sun, 17 Mar 2002 10:32:07 -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 g2HFV2M27027; Sun, 17 Mar 2002 10:31:03 -0500 Received: from crufty.research.bell-labs.com (crufty.research.bell-labs.com [204.178.16.49]) by share.research.bell-labs.com (8.11.6/8.11.6) with SMTP id g2HFU1M27014 for ; Sun, 17 Mar 2002 10:30:01 -0500 Received: from lists.bell-labs.com ([135.104.27.211]) by crufty; Sun Mar 17 10:28:02 EST 2002 Received: by lists.bell-labs.com (Postfix) id 50A354439E; Sun, 17 Mar 2002 10:28:02 -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 1FD814439D for ; Sun, 17 Mar 2002 10:28:02 -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 g2HFS0o26287 for ; Sun, 17 Mar 2002 10:28:00 -0500 (EST) Received: from lucent.com by ih2mail.ih.lucent.com (8.8.8+Sun/EMS-1.5 sol2) id JAA19712; Sun, 17 Mar 2002 09:27:58 -0600 (CST) Message-ID: <3C94B5EA.749EEFA2@lucent.com> From: Alec Brusilovsky Organization: Lucent Technologies X-Mailer: Mozilla 4.77 [en] (Windows NT 5.0; U) X-Accept-Language: en,ru,uk MIME-Version: 1.0 To: SPIRITS list Content-Type: multipart/mixed; boundary="------------A65A1B445B95816B2579BE3F" Subject: [SPIRITS] Another issue 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: Sun, 17 Mar 2002 09:27:39 -0600 This is a multi-part message in MIME format. --------------A65A1B445B95816B2579BE3F Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Ladies and Gentlemen, Initially, we put a good portion of the IN information into the Protocol I-D. However, it seems like this information is taking too much space and bandwidth there. I think that Protocol specs should not educate readers on IN, but provide an adequate reference to where such source of educational material is available. Should we decompose the IN description, INAP parameters, and their encoding into XML, including DTD examples (basically Section 2.0 and Appendix A, B of the SPIRITS Protocol I-D ) into a separate I-D with intent to publish it as an Informational RFC? This document will, also, have material from the following I-Ds: 1. Generating the INAP parameters for the SPIRITS protocol 2. On selection of IN parameters to be carried by the SPIRITS protocol Both of these I-D's have quite valuable and of use to SPIRITS information on PSTN/IN, INAP parameters description, examples of INAP encoding into XML and examples of using automatic tools from ITU-T to generate XML DTDs from INAP UML. Advantages: Localized changes, easier maintenance, reduction in size of the protocol specification, uniform reference from other I-Ds (or RFCs), speeding up SPIRITS specs development. Disadvantages: Dependency. Any opinions? Regards, Alec --------------A65A1B445B95816B2579BE3F Content-Type: text/x-vcard; charset=us-ascii; name="abrusilovsky.vcf" Content-Description: Card for Alec Brusilovsky Content-Disposition: attachment; filename="abrusilovsky.vcf" Content-Transfer-Encoding: 7bit begin:vcard n:Brusilovsky;Alec tel;fax:+1 630 713 5840 tel;work:+1 630 713 8401 x-mozilla-html:FALSE org:e-Services Group;Next Generation Evolution and Architecture version:2.1 email;internet:abrusilovsky@lucent.com title:MTS adr;quoted-printable:;;Room 6H-438=0D=0A2000 Lucent Lane,;Naperville;IL;60566;U S x-mozilla-cpt:;5280 fn:Alec Brusilovsky end:vcard --------------A65A1B445B95816B2579BE3F-- _______________________________________________ SPIRITS mailing list SPIRITS@lists.bell-labs.com http://lists.bell-labs.com/mailman/listinfo/spirits From spirits-admin@lists.bell-labs.com Thu Mar 21 10:26:47 2002 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 KAA13671 for ; Thu, 21 Mar 2002 10:26:47 -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 g2LFQ2M18653; Thu, 21 Mar 2002 10:26:02 -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 SMTP id g2KFhfM12599 for ; Wed, 20 Mar 2002 10:43:42 -0500 Received: from lists.bell-labs.com ([135.104.27.211]) by dirty; Wed Mar 20 10:42:03 EST 2002 Received: by lists.bell-labs.com (Postfix) id EC0724439E; Wed, 20 Mar 2002 10:41:44 -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 9A83E4439D for ; Wed, 20 Mar 2002 10:41:43 -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 SMTP id g2KFffk90576 for ; Wed, 20 Mar 2002 10:41:41 -0500 (EST) Received: from web20604.mail.yahoo.com ([216.136.226.162]) by dusty; Wed Mar 20 10:37:35 EST 2002 Message-ID: <20020320154130.52276.qmail@web20604.mail.yahoo.com> Received: from [166.63.187.71] by web20604.mail.yahoo.com via HTTP; Wed, 20 Mar 2002 07:41:30 PST From: Vijay Gurbani To: seancolson@yahoo.com Cc: Gonzalo.Camarillo@lmf.ericsson.se, sip@ietf.org, spirits@lists.bell-labs.com MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Subject: [SPIRITS] Re: [Sip] Requirements on Reason information. New I-D 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, 20 Mar 2002 07:41:30 -0800 (PST) Sean Olson wrote: >This is a very slippery slope. Although it is >just as problematic, I would prefer the use of >the Server: header for this task. The less the >PSTN pollutes the SIP protocol, the better. Sean: In principal, I agree with you a 100%. However, reality is that for better or for worse, in the near tearm, SIP will have accomodate other networks. Usage of the Reason header in conjunction with interworking with foreign networks is sufficiently "off the beaten" path so that folks implementing baseline SIP do not have to worry about it if they do not want to. In any case, I do not want to start a war on the merits or demerits of SIP interworking with other protocols; just want to point out that the Reason header could be used successfully in those cases. Regards, - vijay ===== - vijay -- Vijay K. Gurbani vgurbani@yahoo.com __________________________________________________ Do You Yahoo!? Yahoo! Sports - live college hoops coverage http://sports.yahoo.com/ _______________________________________________ SPIRITS mailing list SPIRITS@lists.bell-labs.com http://lists.bell-labs.com/mailman/listinfo/spirits From spirits-admin@lists.bell-labs.com Thu Mar 21 10:27:40 2002 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 KAA13707 for ; Thu, 21 Mar 2002 10:27:39 -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 g2LFRZM18670; Thu, 21 Mar 2002 10:27:35 -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 SMTP id g2KFjgM12631 for ; Wed, 20 Mar 2002 10:45:42 -0500 Received: from lists.bell-labs.com ([135.104.27.211]) by dirty; Wed Mar 20 10:45:31 EST 2002 Received: by lists.bell-labs.com (Postfix) id 888284439E; Wed, 20 Mar 2002 10:45:08 -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 621A04439D for ; Wed, 20 Mar 2002 10:45:08 -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 SMTP id g2KFj5o81662 for ; Wed, 20 Mar 2002 10:45:06 -0500 (EST) Received: from web20610.mail.yahoo.com ([216.136.226.168]) by dusty; Wed Mar 20 10:40:58 EST 2002 Message-ID: <20020320154440.32098.qmail@web20610.mail.yahoo.com> Received: from [166.63.187.71] by web20610.mail.yahoo.com via HTTP; Wed, 20 Mar 2002 07:44:39 PST From: Vijay Gurbani To: spirits@lists.bell-labs.com MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Subject: [SPIRITS] Re: [Sip] Requirements on Reason information. New I-D 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, 20 Mar 2002 07:44:39 -0800 (PST) I mistakenly CC'd this to spirits@lists.bell-lab.com, which bounced back -- for those on the spirits WG list following this thread, here is the start of the thread. - vijay Gonzalo Camarillo wrote: > > Chairmen, [...] > I have put together an I-D with those requirements. > > http://standards.ericsson.net/gonzalo/draft-camarillo-sipping-reason-00.txt > > I would like to know if these requirements are what you expected or if, > on the other hand, you wanted something else... > > I intend to submit this draft, including the comments I may receive, on > Monday. One more service that can be added in Section 5 of your I-D is SPIRITS-based services. A UA getting an INVITE may benefit from having a Reason header to make a determination if the invitation resulted from the PSTN domain. Likewise the header may help UACs that get a final response from a SIP/IN entity. Regards, - vijay ===== - vijay -- Vijay K. Gurbani vgurbani@yahoo.com __________________________________________________ Do You Yahoo!? Yahoo! Sports - live college hoops coverage http://sports.yahoo.com/ _______________________________________________ SPIRITS mailing list SPIRITS@lists.bell-labs.com http://lists.bell-labs.com/mailman/listinfo/spirits From spirits-admin@lists.bell-labs.com Thu Mar 21 10:27:48 2002 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 KAA13723 for ; Thu, 21 Mar 2002 10:27:48 -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 g2LFReM18685; Thu, 21 Mar 2002 10:27:40 -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 SMTP id g2KFpgM12671 for ; Wed, 20 Mar 2002 10:51:42 -0500 Received: from lists.bell-labs.com ([135.104.27.211]) by dirty; Wed Mar 20 10:50:39 EST 2002 Received: by lists.bell-labs.com (Postfix) id 03E214439E; Wed, 20 Mar 2002 10:50:20 -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 D334B4439D for ; Wed, 20 Mar 2002 10:50:19 -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 SMTP id g2KFoIk91204 for ; Wed, 20 Mar 2002 10:50:18 -0500 (EST) Received: from web11605.mail.yahoo.com ([216.136.172.57]) by dusty; Wed Mar 20 10:46:11 EST 2002 Message-ID: <20020320155013.94640.qmail@web11605.mail.yahoo.com> Received: from [166.63.189.85] by web11605.mail.yahoo.com via HTTP; Wed, 20 Mar 2002 07:50:13 PST From: Sean Olson To: Vijay Gurbani Cc: Gonzalo.Camarillo@lmf.ericsson.se, sip@ietf.org, spirits@lists.bell-labs.com In-Reply-To: <20020320154130.52276.qmail@web20604.mail.yahoo.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Subject: [SPIRITS] Re: [Sip] Requirements on Reason information. New I-D 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, 20 Mar 2002 07:50:13 -0800 (PST) I understand the problem you want to solve. I have no issue with interworking with other networks. My main issue is attempting to *identify* the network you are interworking with via the Reason: header. This is the slippery slope I want to avoid. It quickly becomes very nasty in more complex topologies where you may dip into the PSTN-space more than once. /sean --- Vijay Gurbani wrote: > Sean Olson wrote: > >This is a very slippery slope. Although it is > >just as problematic, I would prefer the use of > >the Server: header for this task. The less the > >PSTN pollutes the SIP protocol, the better. > > Sean: > > In principal, I agree with you a 100%. However, > reality is that for better or for worse, in the near > tearm, SIP will have accomodate other networks. > > Usage of the Reason header in conjunction with > interworking with foreign networks is sufficiently > "off the beaten" path so that folks implementing > baseline SIP do not have to worry about it if they > do > not want to. > > In any case, I do not want to start a war on the > merits or demerits of SIP interworking with other > protocols; just want to point out that the Reason > header could be used successfully in those cases. > > Regards, > > - vijay > > > ===== > - vijay > -- > Vijay K. Gurbani > vgurbani@yahoo.com > > __________________________________________________ > Do You Yahoo!? > Yahoo! Sports - live college hoops coverage > http://sports.yahoo.com/ > > _______________________________________________ > Sip mailing list > https://www1.ietf.org/mailman/listinfo/sip > This list is for NEW development of the core SIP > Protocol > Use sip-implementors@cs.columbia.edu for questions > on current sip > Use sipping@ietf.org for new developments on the > application of sip ===== Sean Olson __________________________________________________ Do You Yahoo!? Yahoo! Sports - live college hoops coverage http://sports.yahoo.com/ _______________________________________________ SPIRITS mailing list SPIRITS@lists.bell-labs.com http://lists.bell-labs.com/mailman/listinfo/spirits From spirits-admin@lists.bell-labs.com Tue Mar 26 10:58:49 2002 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 KAA08100 for ; Tue, 26 Mar 2002 10:58:48 -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 g2QFw2M20691; Tue, 26 Mar 2002 10:58:02 -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 SMTP id g2QFvdM20678 for ; Tue, 26 Mar 2002 10:57:40 -0500 Received: from lists.bell-labs.com ([135.104.27.211]) by dirty; Tue Mar 26 10:57:30 EST 2002 Received: by lists.bell-labs.com (Postfix) id 1DE264439E; Tue, 26 Mar 2002 10:57:08 -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 EC1EC4439D for ; Tue, 26 Mar 2002 10:57:07 -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 SMTP id g2QFv6o95620 for ; Tue, 26 Mar 2002 10:57:06 -0500 (EST) Received: from web12403.mail.yahoo.com ([216.136.173.130]) by dusty; Tue Mar 26 10:52:55 EST 2002 Message-ID: <20020326155701.83284.qmail@web12403.mail.yahoo.com> Received: from [128.238.34.121] by web12403.mail.yahoo.com via HTTP; Tue, 26 Mar 2002 07:57:01 PST From: Zhifeng Tao To: spirits@lists.bell-labs.com MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Subject: [SPIRITS] about test result analysis for SS7 testing 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, 26 Mar 2002 07:57:01 -0800 (PST) Hi, Is there any tesing product in current market that supports test data analysis for SS7 testing? For example, if we have executed some test based upon the test plan and collected a bunch of data, can any product analyze the correctness of the test result? Or some off-the-shelf product has already included the functions of automatic testing execution and post-test data analysis? Thanks, Jeff __________________________________________________ Do You Yahoo!? Yahoo! Movies - coverage of the 74th Academy Awards® http://movies.yahoo.com/ _______________________________________________ SPIRITS mailing list SPIRITS@lists.bell-labs.com http://lists.bell-labs.com/mailman/listinfo/spirits From spirits-admin@lists.bell-labs.com Tue Mar 26 16:02:26 2002 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 QAA23603 for ; Tue, 26 Mar 2002 16:02:26 -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 g2QL21M22014; Tue, 26 Mar 2002 16:02: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 SMTP id g2QL1dM22001 for ; Tue, 26 Mar 2002 16:01:39 -0500 Received: from lists.bell-labs.com ([135.104.27.211]) by dirty; Tue Mar 26 16:01:12 EST 2002 Received: by lists.bell-labs.com (Postfix) id 6FDCA4439E; Tue, 26 Mar 2002 16:00: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 40EB64439D for ; Tue, 26 Mar 2002 16:00:49 -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 SMTP id g2QL0mk36034 for ; Tue, 26 Mar 2002 16:00:48 -0500 (EST) Received: from berkshire.research.att.com ([135.207.23.61]) by dusty; Tue Mar 26 15:56:37 EST 2002 Received: from research.att.com (localhost [127.0.0.1]) by berkshire.research.att.com (Postfix) with ESMTP id 595A97B4B for ; Tue, 26 Mar 2002 16:00:45 -0500 (EST) X-Mailer: exmh version 2.5 07/13/2001 with nmh-1.0.4 From: Steve Bellovin To: spirits@lists.bell-labs.com Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Message-Id: <20020326210045.595A97B4B@berkshire.research.att.com> Subject: [SPIRITS] rfc author instructions 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, 26 Mar 2002 16:00:45 -0500 There are some new policies and guidelines on RFCs that authors should note. Quite simply, the IESG and the RFC editor will not publish documents that do not conform to these policies. (Note that I'm wearing my co-chair hat when I say this, not my IESG hat -- I don't have the ability to change these policies.) The most problematic, for some people and some documents, is the restriction on the number of authors for an RFC. The intent is that the "author" list on the title page be limited to those who have actually contributed a significant amount of text. If there are a lot of people who have contributed text, the recommended solution is to list one or two people as "editors", and have a "contributors" section that lists everyone else. http://www.rfc-editor.org/policy.html http://www.ietf.org/ID-nits.html --Steve Bellovin, http://www.research.att.com/~smb Full text of "Firewalls" book now at http://www.wilyhacker.com _______________________________________________ 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 27 02:52:16 2002 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 CAA18468 for ; Wed, 27 Mar 2002 02:52:16 -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 g2R7q1M24774; Wed, 27 Mar 2002 02:52: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 SMTP id g2R7pcM24761 for ; Wed, 27 Mar 2002 02:51:38 -0500 Received: from lists.bell-labs.com ([135.104.27.211]) by dirty; Wed Mar 27 02:51:39 EST 2002 Received: by lists.bell-labs.com (Postfix) id 396E34439E; Wed, 27 Mar 2002 02:51:17 -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 108134439D for ; Wed, 27 Mar 2002 02:51:17 -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 SMTP id g2R7pFk73149 for ; Wed, 27 Mar 2002 02:51:15 -0500 (EST) Received: from obsoft.com ([64.139.4.113]) by dusty; Wed Mar 27 02:47:05 EST 2002 Received: from obsoft.com (localhost.localdomain [127.0.0.1]) by obsoft.com (8.11.6/8.11.6) with ESMTP id g2R7u3t17394; Tue, 26 Mar 2002 23:56:03 -0800 Message-ID: <3CA17B13.BA7609A9@obsoft.com> From: Bobby Sardana Organization: ObjectSoftware, Inc X-Mailer: Mozilla 4.78 [en] (X11; U; Linux 2.4.7-10 i686) X-Accept-Language: en MIME-Version: 1.0 To: Zhifeng Tao Cc: spirits@lists.bell-labs.com Subject: Re: [SPIRITS] about test result analysis for SS7 testing References: <20020326155701.83284.qmail@web12403.mail.yahoo.com> Content-Type: text/plain; charset=iso-8859-1 X-MIME-Autoconverted: from 8bit to quoted-printable by obsoft.com id g2R7u3t17394 Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from quoted-printable to 8bit by share.research.bell-labs.com id g2R7pdM24762 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, 26 Mar 2002 23:56:03 -0800 Content-Transfer-Encoding: 8bit In the past, I have used the following two SS7 simulators that provide a wide range of functionality: a. MGTS by Tekelec b. INET by Inet See if the can solve the functionality you need. regards, Bobby Sardana. sardana@obsoft.com Zhifeng Tao wrote: > Hi, > > Is there any tesing product in current market that > supports test data analysis for SS7 testing? For > example, if we have executed some test based upon the > test plan and collected a bunch of data, can any > product analyze the correctness of the test result? > Or some off-the-shelf product has already included the > functions of automatic testing execution and post-test > data analysis? > > Thanks, > > Jeff > > __________________________________________________ > Do You Yahoo!? > Yahoo! Movies - coverage of the 74th Academy Awards® > http://movies.yahoo.com/ > _______________________________________________ > 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 Thu Mar 28 16:49:08 2002 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 QAA17103 for ; Thu, 28 Mar 2002 16:49:08 -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 g2SLm2M02260; Thu, 28 Mar 2002 16:48:02 -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 SMTP id g2SLleM02247 for ; Thu, 28 Mar 2002 16:47:40 -0500 Received: from lists.bell-labs.com ([135.104.27.211]) by dirty; Thu Mar 28 16:47:30 EST 2002 Received: by lists.bell-labs.com (Postfix) id 0099F4439E; Thu, 28 Mar 2002 16:47:09 -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 CE70B4439D for ; Thu, 28 Mar 2002 16:47:08 -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 g2SLl7o06517 for ; Thu, 28 Mar 2002 16:47:07 -0500 (EST) Received: from lucent.com by ih2mail.ih.lucent.com (8.8.8+Sun/EMS-1.5 sol2) id PAA25085; Thu, 28 Mar 2002 15:47:05 -0600 (CST) Message-ID: <3CA38F35.5B915C97@lucent.com> From: Alec Brusilovsky Organization: Lucent Technologies X-Mailer: Mozilla 4.77 [en] (Windows NT 5.0; U) X-Accept-Language: en,ru,uk MIME-Version: 1.0 To: SPIRITS list Cc: Steve Bellovin Content-Type: multipart/mixed; boundary="------------AEA068F4A9F24C9F9EA870D5" Subject: [SPIRITS] 3/19 meeting summary 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: Thu, 28 Mar 2002 15:46:29 -0600 This is a multi-part message in MIME format. --------------AEA068F4A9F24C9F9EA870D5 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Ladies and Gentlemen, Please review a brief summary of our Minneapolis meeting on March 19. The discussion at the meeting stemmed from the SPIRITS Protocol I-D: http://www.ietf.org/internet-drafts/draft-gurbani-spirits-protocol-01.txt 1. Keep SPIRITS Event package as part of the SPIRITS protocol I-D, as opposed to splitting it into a separate I-D to develop in parallel; 2. Split IN description, parameters, information flows, etc. from the protocol I-D, combine this material with IN and XML encoding related material from draft-ietf-spirits-in-02.txt and draft-unmehopa-spirits-parameter-generation-00 Both of these I-D's have valuable information on PSTN/IN, INAP parameters description, examples of INAP encoding into XML and examples of using automatic tools from ITU-T to generate XML DTDs from INAP ASN.1. Advantages: localized changes, easier maintenance, reduction in size of the protocol specification, uniform reference from other I-Ds (or RFCs) (SIN?), speeding up SPIRITS specs development. Disadvantages: dependency. The resulting I-D to be submitted to the IESG as an Informational RFC candidate before the next meeting. Musa Unmehopa and Kumar Vemuri volunteered to lead this work. 3. ICIDD is a better example of SPIRITS service than ICW. Vijay presented ICIDD service example utilizing TAA at the meeting; 4. Existing MIME types seem to be sufficient for SPIRITS. No compelling need to invent another one; 5. There is an urgent need to define parameter lists, corresponding XML DTDs and Schemas for SUBSCRIBE methods; 6. SPIRITS security might rely on SIP security with exception of Interface B that traverses both administrative and PSTN/IP domains. 7. When dealing with IANA issues, protocol document editors have to be explicitly clear and define sufficiently what needs to be registered; It was a good working meeting with about 100 attendants. What's next? Continue protocol development. We plan to submit SPIRITS Protocol I-D to the IESG in three to six months, preferably, together with SPIRITS MIB I-D. We need help with Wireless events and their specific parameters, need help with expanding the Security Considerations section, and we really need volunteers to assist/drive with MIB. Please contact Steve or myself if you would like to volunteer. Kind regards, Alec --------------AEA068F4A9F24C9F9EA870D5 Content-Type: text/x-vcard; charset=us-ascii; name="abrusilovsky.vcf" Content-Description: Card for Alec Brusilovsky Content-Disposition: attachment; filename="abrusilovsky.vcf" Content-Transfer-Encoding: 7bit begin:vcard n:Brusilovsky;Alec tel;fax:+1 630 713 5840 tel;work:+1 630 713 8401 x-mozilla-html:FALSE org:e-Services Group;Next Generation Evolution and Architecture version:2.1 email;internet:abrusilovsky@lucent.com title:MTS adr;quoted-printable:;;Room 6H-438=0D=0A2000 Lucent Lane,;Naperville;IL;60566;U S x-mozilla-cpt:;5280 fn:Alec Brusilovsky end:vcard --------------AEA068F4A9F24C9F9EA870D5-- _______________________________________________ SPIRITS mailing list SPIRITS@lists.bell-labs.com http://lists.bell-labs.com/mailman/listinfo/spirits From spirits-admin@lists.bell-labs.com Thu Mar 28 16:58:11 2002 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 QAA17463 for ; Thu, 28 Mar 2002 16:58:10 -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 g2SLw1M02329; Thu, 28 Mar 2002 16:58: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 SMTP id g2SLvdM02316 for ; Thu, 28 Mar 2002 16:57:39 -0500 Received: from lists.bell-labs.com ([135.104.27.211]) by dirty; Thu Mar 28 16:57:05 EST 2002 Received: by lists.bell-labs.com (Postfix) id 0FC6D4439E; Thu, 28 Mar 2002 16:56:44 -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 E06D64439D for ; Thu, 28 Mar 2002 16:56:43 -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 g2SLugo07114 for ; Thu, 28 Mar 2002 16:56:42 -0500 (EST) Received: from lucent.com by ih2mail.ih.lucent.com (8.8.8+Sun/EMS-1.5 sol2) id PAA29089; Thu, 28 Mar 2002 15:56:40 -0600 (CST) Message-ID: <3CA39194.20702@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:0.9.4) Gecko/20011128 Netscape6/6.2.1 X-Accept-Language: en-us MIME-Version: 1.0 To: Alec Brusilovsky Cc: SPIRITS list , Steve Bellovin Subject: Re: [SPIRITS] 3/19 meeting summary References: <3CA38F35.5B915C97@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: Thu, 28 Mar 2002 15:56:36 -0600 Content-Transfer-Encoding: 7bit Alec Brusilovsky wrote: > Ladies and Gentlemen, > > Please review a brief summary of our Minneapolis meeting on > March 19. Alec: One correction, as follows: > 4. Existing MIME types seem to be sufficient for SPIRITS. No > compelling need to invent another one; My recollection differs; I left it as an open issue saying that if anyone knows a MIME type we can (re)use, please let me know. Otherwise, we will have to register application/spirits-event as a new MIME type. Thanks, - vijay -- Vijay K. Gurbani vkg@{lucent.com,research.bell-labs.com,acm.org} Internet Software and eServices Group Lucent Technologies/Bell Labs Innovations, 2000 Lucent Lane, Rm 6G-440 Naperville, Illinois 60566 Voice: +1 630 224 0216 Fax: +1 630 713 0184 _______________________________________________ SPIRITS mailing list SPIRITS@lists.bell-labs.com http://lists.bell-labs.com/mailman/listinfo/spirits From spirits-admin@lists.bell-labs.com Thu Mar 28 17:40:04 2002 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 RAA18463 for ; Thu, 28 Mar 2002 17:40: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 g2SMe2M02670; Thu, 28 Mar 2002 17:40:02 -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 SMTP id g2SMdeM02648 for ; Thu, 28 Mar 2002 17:39:40 -0500 Received: from lists.bell-labs.com ([135.104.27.211]) by dirty; Thu Mar 28 17:38:41 EST 2002 Received: by lists.bell-labs.com (Postfix) id 0BEF74439E; Thu, 28 Mar 2002 17:38:20 -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 DC9654439D for ; Thu, 28 Mar 2002 17:38:19 -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 g2SMcIo09851 for ; Thu, 28 Mar 2002 17:38:18 -0500 (EST) Received: from lucent.com by ih2mail.ih.lucent.com (8.8.8+Sun/EMS-1.5 sol2) id QAA15489; Thu, 28 Mar 2002 16:38:15 -0600 (CST) Message-ID: <3CA39B56.69E6DD08@lucent.com> From: Alec Brusilovsky Organization: Lucent Technologies X-Mailer: Mozilla 4.77 [en] (Windows NT 5.0; U) X-Accept-Language: en,ru,uk MIME-Version: 1.0 To: "Vijay K. Gurbani" Cc: SPIRITS list , Steve Bellovin Subject: Re: [SPIRITS] 3/19 meeting summary References: <3CA38F35.5B915C97@lucent.com> <3CA39194.20702@lucent.com> Content-Type: multipart/mixed; boundary="------------80243083BB5A57527E781DE9" 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: Thu, 28 Mar 2002 16:38:14 -0600 This is a multi-part message in MIME format. --------------80243083BB5A57527E781DE9 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Vijay, It seems like you are right. I checked my note and the MIME type was not decided at the meeting, but rather deferred to the online discussion. However, it would be truly nice to be able to reuse an existing MIME type. Thanks for the correction, Alec "Vijay K. Gurbani" wrote: > Alec Brusilovsky wrote: > > > Ladies and Gentlemen, > > > > Please review a brief summary of our Minneapolis meeting on > > March 19. > > Alec: > > One correction, as follows: > > > 4. Existing MIME types seem to be sufficient for SPIRITS. No > > compelling need to invent another one; > > My recollection differs; I left it as an open issue saying > that if anyone knows a MIME type we can (re)use, please let me know. > Otherwise, we will have to register application/spirits-event > as a new MIME type. > > Thanks, > > - vijay > -- > Vijay K. Gurbani vkg@{lucent.com,research.bell-labs.com,acm.org} > Internet Software and eServices Group > Lucent Technologies/Bell Labs Innovations, 2000 Lucent Lane, Rm 6G-440 > Naperville, Illinois 60566 Voice: +1 630 224 0216 Fax: +1 630 713 0184 --------------80243083BB5A57527E781DE9 Content-Type: text/x-vcard; charset=us-ascii; name="abrusilovsky.vcf" Content-Description: Card for Alec Brusilovsky Content-Disposition: attachment; filename="abrusilovsky.vcf" Content-Transfer-Encoding: 7bit begin:vcard n:Brusilovsky;Alec tel;fax:+1 630 713 5840 tel;work:+1 630 713 8401 x-mozilla-html:FALSE org:e-Services Group;Next Generation Evolution and Architecture version:2.1 email;internet:abrusilovsky@lucent.com title:MTS adr;quoted-printable:;;Room 6H-438=0D=0A2000 Lucent Lane,;Naperville;IL;60566;U S x-mozilla-cpt:;5280 fn:Alec Brusilovsky end:vcard --------------80243083BB5A57527E781DE9-- _______________________________________________ SPIRITS mailing list SPIRITS@lists.bell-labs.com http://lists.bell-labs.com/mailman/listinfo/spirits