From extest-admin@lists.bell-labs.com Wed Aug 1 05:04:01 2001 Received: from lists.bell-labs.com (share.research.bell-labs.com [204.178.16.58]) by ietf.org (8.9.1a/8.9.1a) with SMTP id FAA23137 for ; Wed, 1 Aug 2001 05:04:01 -0400 (EDT) Received: from share.research.bell-labs.com (localhost.localdomain [127.0.0.1]) by lists.bell-labs.com (Postfix) with ESMTP id 6E17A4449D for ; Wed, 1 Aug 2001 05:04:05 -0400 (EDT) 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.0beta6 Precedence: bulk Message-Id: <20010801090405.6E17A4449D@lists.bell-labs.com> Date: Wed, 1 Aug 2001 05:04:05 -0400 (EDT) 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 QMKP http://lists.bell-labs.com/mailman/options/spirits/spirits-archive%40lists.ietf.org From spirits-admin@lists.bell-labs.com Fri Aug 3 09:27:59 2001 Received: from lists.bell-labs.com (share.research.bell-labs.com [204.178.16.58]) by ietf.org (8.9.1a/8.9.1a) with SMTP id JAA15566 for ; Fri, 3 Aug 2001 09:27:59 -0400 (EDT) Received: from share.research.bell-labs.com (localhost.localdomain [127.0.0.1]) by lists.bell-labs.com (Postfix) with ESMTP id 2BB564433A; Fri, 3 Aug 2001 09:29:02 -0400 (EDT) Delivered-To: spirits@lists.bell-labs.com Received: from znsgs0ja.europe.nortel.com (unknown [47.165.25.40]) by lists.bell-labs.com (Postfix) with ESMTP id 9335744336; Fri, 3 Aug 2001 09:28:05 -0400 (EDT) Received: from qnsgs000.nortel.com (znsgs016 [47.255.64.31]) by znsgs0ja.europe.nortel.com (8.11.0/8.11.0) with ESMTP id f73DRsg03623; Fri, 3 Aug 2001 14:27:54 +0100 (BST) Received: from nwcwi1a.europe.nortel.com by qnsgs000.nortel.com; Fri, 3 Aug 2001 14:27:31 +0100 Received: by nwcwi1a.europe.nortel.com with Internet Mail Service (5.5.2653.19) id ; Fri, 3 Aug 2001 14:27:04 +0100 Message-ID: From: "Michael O'Doherty" To: "'faynberg@lucent.com'" , spirits@lists.bell-labs.com Cc: pint@lists.bell-labs.com Subject: RE: [SPIRITS] Half-Pint MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2653.19) Content-Type: multipart/alternative; boundary="----_=_NextPart_001_01C11C1F.FA5FA2A0" 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.0beta6 Precedence: bulk Reply-To: spirits@lists.bell-labs.com List-Help: List-Post: List-Subscribe: , List-Id: IETF SPIRITS Working Group List-Unsubscribe: , List-Archive: http://lists.bell-labs.com/pipermail/spirits/ Date: Fri, 3 Aug 2001 14:27:01 +0100 This message is in MIME format. Since your mail reader does not understand this format, some or all of this message may not be legible. ------_=_NextPart_001_01C11C1F.FA5FA2A0 Content-Type: text/plain; charset="iso-8859-1" Hi, The Half-Pint internet draft is now properly formatted (more or less) and available at: http://search.ietf.org/internet-drafts/draft-odoherty-half-pint-00.txt The idea behind the protocol is to try to provide something relatively lightweight which will still provide a useful set of services for a developer tying together web and PSTN services. The approach is to trade off flexibility and completeness for simplicity - hence the name (which is not cast in stone). My feeling is that this protocol, while not having the same ultimate flexibility is simpler to get up and running today than a Pint/Spirits like approach, especially from the perspective of a web developer. Part of the thinking is that it is relatively well bounded and part of it is that it avoids using SIP as a transport as SIP is not quite mature enough or deployed enough today for the task - I'd be very interested to hear comments on this view - is there anyone who feels that it would be better to use SIP as the transport, maybe extending Pint ? The main aim is to get something working quickly (say within four months as a goal) that provides the type of functionality contained in the half-pint draft and allows service developers to start their work, and that has some sort of consensus behind it from a standards point of view. If anybody has views on this approach or on better ways to achieve the same goal, I'd be very happy to work with you to try to meet these objectives. Cheers, Mick. ------_=_NextPart_001_01C11C1F.FA5FA2A0 Content-Type: text/html; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable RE: [SPIRITS] Half-Pint

Hi,

The Half-Pint internet draft is now properly = formatted (more or less) and available at:

http://search.ietf.org/internet-drafts/draft-odoherty-= half-pint-00.txt

The idea behind the protocol is to try to provide = something relatively lightweight which will still provide a useful set = of services for a developer tying together web and PSTN services. The = approach is to trade off flexibility and completeness for simplicity - = hence the name (which is not cast in stone).

My feeling is that this protocol, while not having = the same ultimate flexibility is simpler to get up and running today = than a Pint/Spirits like approach, especially from the perspective of a = web developer. Part of the thinking is that it is relatively well = bounded and part of it is that it avoids using SIP as a transport as = SIP is not quite mature enough or deployed enough today for the task - = I'd be very interested to hear comments on this view - is there anyone = who feels that it would be better to use SIP as the transport, maybe = extending Pint ?

The main aim is to get something working quickly (say = within four months as a goal) that provides the type of functionality = contained in the half-pint draft and allows service developers to start = their work, and that has some sort of consensus behind it from a = standards point of view.

If anybody has views on this approach or on better = ways to achieve the same goal, I'd be very happy to work with you to = try to meet these objectives.

Cheers,

Mick.


------_=_NextPart_001_01C11C1F.FA5FA2A0-- _______________________________________________ SPIRITS mailing list SPIRITS@lists.bell-labs.com http://lists.bell-labs.com/mailman/listinfo/spirits From spirits-admin@lists.bell-labs.com Sat Aug 4 11:46:57 2001 Received: from lists.bell-labs.com (share.research.bell-labs.com [204.178.16.58]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA27715 for ; Sat, 4 Aug 2001 11:46:56 -0400 (EDT) Received: from share.research.bell-labs.com (localhost.localdomain [127.0.0.1]) by lists.bell-labs.com (Postfix) with ESMTP id 3F0434433A; Sat, 4 Aug 2001 11:48:02 -0400 (EDT) Delivered-To: spirits@lists.bell-labs.com Received: from voyager.ashleylaurent.com (goodhope.vpcom.com [207.207.28.147]) by lists.bell-labs.com (Postfix) with ESMTP id B65FA44336 for ; Sat, 4 Aug 2001 11:47:55 -0400 (EDT) MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Message-ID: <387DCE97A6A6CC40B4A6E090A955B5E02561E9@voyager.ashleylaurent.com> X-MimeOLE: Produced By Microsoft Exchange V6.0.4417.0 content-class: urn:content-classes:message Thread-Topic: about PSTN specification Thread-Index: AcEc/K/icsOT09KjR5mSLA0Ac9Z2pw== From: "Na Li" To: Subject: [SPIRITS] about PSTN specification 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.0beta6 Precedence: bulk Reply-To: spirits@lists.bell-labs.com List-Help: List-Post: List-Subscribe: , List-Id: IETF SPIRITS Working Group List-Unsubscribe: , List-Archive: http://lists.bell-labs.com/pipermail/spirits/ Date: Sat, 4 Aug 2001 10:46:55 -0500 Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from quoted-printable to 8bit by ietf.org id LAA27715 Hello, Could anyone tell me what is the standard for PBX and class 5 switch, the interface between normal phone and PBX, and the interface between PBX to CO class 5 switch? I am very interested in the Voice over IP and the interworking between VoIP and PSTN. To start, I think I need to know how the PSTN works. If you can recommand some good books, that would be great. I have read some books. They are good in providing the concept, but too general. Thanks a lot for your help, have a nice weekend, Lina _______________________________________________ SPIRITS mailing list SPIRITS@lists.bell-labs.com http://lists.bell-labs.com/mailman/listinfo/spirits From spirits-admin@lists.bell-labs.com Sun Aug 5 16:18:58 2001 Received: from lists.bell-labs.com (share.research.bell-labs.com [204.178.16.58]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA20238 for ; Sun, 5 Aug 2001 16:18:57 -0400 (EDT) Received: from share.research.bell-labs.com (localhost.localdomain [127.0.0.1]) by lists.bell-labs.com (Postfix) with ESMTP id 2791244338; Sun, 5 Aug 2001 16:20:02 -0400 (EDT) Delivered-To: spirits@share.research.bell-labs.com Received: from crufty.research.bell-labs.com (crufty.research.bell-labs.com [204.178.16.49]) by lists.bell-labs.com (Postfix) with SMTP id 88D5544336 for ; Sun, 5 Aug 2001 16:19:20 -0400 (EDT) Received: from lists.bell-labs.com ([135.104.27.211]) by crufty; Sun Aug 5 16:14:18 EDT 2001 Received: by lists.bell-labs.com (Postfix) id 8C44544394; Sun, 5 Aug 2001 16:04:28 -0400 (EDT) Delivered-To: spirits@lists.bell-labs.com Received: from ih2mail.ih.lucent.com (ih2mail.ih.lucent.com [135.1.241.39]) by lists.bell-labs.com (Postfix) with ESMTP id 2300044393 for ; Sun, 5 Aug 2001 16:04:28 -0400 (EDT) Received: from lucent.com by ih2mail.ih.lucent.com (8.8.8+Sun/EMS-1.5 sol2) id PAA10012; Sun, 5 Aug 2001 15:04:25 -0500 (CDT) Message-ID: <3B6DA778.2D3B2E4@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@lists.bell-labs.com Subject: Re: [SPIRITS] about PSTN specification References: <387DCE97A6A6CC40B4A6E090A955B5E02561E9@voyager.ashleylaurent.com> Content-Type: multipart/mixed; boundary="------------F54AB8C0347EFF6DA3B13642" 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.0beta6 Precedence: bulk Reply-To: spirits@lists.bell-labs.com List-Help: List-Post: List-Subscribe: , List-Id: IETF SPIRITS Working Group List-Unsubscribe: , List-Archive: http://lists.bell-labs.com/pipermail/spirits/ Date: Sun, 05 Aug 2001 15:07:21 -0500 This is a multi-part message in MIME format. --------------F54AB8C0347EFF6DA3B13642 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Lina, You might as well start from the good ones... I would highly recommend Igor Faynberg and Hui-Lan Lu's books on IN standards and the second one on PSTN/IP Interworking. Regards, Alec P.S. I cannot recall the titles, but you can plug FAYNBERG into amazon.com and get the exact titles, as well as ISBN codes. Na Li wrote: > Hello, > > Could anyone tell me what is the standard for PBX and class 5 switch, > the interface between normal phone and PBX, and the interface between > PBX to CO class 5 switch? I am very interested in the Voice over IP and > the interworking between VoIP and PSTN. To start, I think I need to know > how the PSTN works. If you can recommand some good books, that would be > great. I have read some books. They are good in providing the concept, > but too general. > > Thanks a lot for your help, have a nice weekend, > > Lina > > _______________________________________________ > SPIRITS mailing list > SPIRITS@lists.bell-labs.com > http://lists.bell-labs.com/mailman/listinfo/spirits --------------F54AB8C0347EFF6DA3B13642 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:;;IHP 1A-423=0D=0A263 Shuman Blvd,P O Box 3050;Naperville;IL;60566-7050;U S x-mozilla-cpt:;5312 fn:Alec Brusilovsky end:vcard --------------F54AB8C0347EFF6DA3B13642-- _______________________________________________ SPIRITS mailing list SPIRITS@lists.bell-labs.com http://lists.bell-labs.com/mailman/listinfo/spirits From spirits-admin@lists.bell-labs.com Wed Aug 29 11:06:32 2001 Received: from lists.bell-labs.com (share.research.bell-labs.com [204.178.16.58]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA00375 for ; Wed, 29 Aug 2001 11:06:32 -0400 (EDT) Received: from share.research.bell-labs.com (localhost.localdomain [127.0.0.1]) by lists.bell-labs.com (Postfix) with ESMTP id D18914434B; Wed, 29 Aug 2001 10:08:04 -0400 (EDT) Delivered-To: spirits@lists.bell-labs.com Received: from znsgs0ja.europe.nortel.com (znsgs0ja.nortelnetworks.com [47.165.25.40]) by lists.bell-labs.com (Postfix) with ESMTP id 3CCA344336; Wed, 29 Aug 2001 10:07:17 -0400 (EDT) Received: from qnsgs000.nortel.com (znsgs016 [47.255.64.31]) by znsgs0ja.europe.nortel.com (8.11.0/8.11.0) with ESMTP id f7TF5xg20590; Wed, 29 Aug 2001 16:05:59 +0100 (BST) Received: from nwcwi1a.europe.nortel.com by qnsgs000.nortel.com; Wed, 29 Aug 2001 16:05:37 +0100 Received: by nwcwi1a.europe.nortel.com with Internet Mail Service (5.5.2653.19) id ; Wed, 29 Aug 2001 16:04:44 +0100 Message-ID: From: "Michael O'Doherty" To: "'spirits@lists.bell-labs.com'" , "'faynberg@lucent.com'" Cc: pint@lists.bell-labs.com Subject: RE: [SPIRITS] Half-Pint MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2653.19) Content-Type: multipart/alternative; boundary="----_=_NextPart_001_01C1309B.F088DD10" 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.0beta6 Precedence: bulk Reply-To: spirits@lists.bell-labs.com List-Help: List-Post: List-Subscribe: , List-Id: IETF SPIRITS Working Group List-Unsubscribe: , List-Archive: http://lists.bell-labs.com/pipermail/spirits/ Date: Wed, 29 Aug 2001 16:04:45 +0100 This message is in MIME format. Since your mail reader does not understand this format, some or all of this message may not be legible. ------_=_NextPart_001_01C1309B.F088DD10 Content-Type: text/plain; charset="iso-8859-1" I thought I would try again with this message as I realize most people were probably tied up in the IETF meetings when I sent it last. In case it is not clear below, I am interested in whatever is the best way to tackle the requirements that the half-pint protocol addresses, whether that be by refining half-pint or by evolving PINT or a SPIRITS like protocol. I think this clearly lines up with the goals of these groups so I'm very keen to get feedback/direction from the lists. ---------------------------------------------------------------------------- --- The Half-Pint internet draft is now properly formatted (more or less) and available at: http://search.ietf.org/internet-drafts/draft-odoherty-half-pint-00.txt The idea behind the protocol is to try to provide something relatively lightweight which will still provide a useful set of services for a developer tying together web and PSTN services. The approach is to trade off flexibility and completeness for simplicity - hence the name (which is not cast in stone). My feeling is that this protocol, while not having the same ultimate flexibility is simpler to get up and running today than a Pint/Spirits like approach, especially from the perspective of a web developer. Part of the thinking is that it is relatively well bounded and part of it is that it avoids using SIP as a transport as SIP is not quite mature enough or deployed enough today for the task - I'd be very interested to hear comments on this view - is there anyone who feels that it would be better to use SIP as the transport, maybe extending Pint ? The main aim is to get something working quickly (say within four months as a goal) that provides the type of functionality contained in the half-pint draft and allows service developers to start their work, and that has some sort of consensus behind it from a standards point of view. If anybody has views on this approach or on better ways to achieve the same goal, I'd be very happy to work with you to try to meet these objectives. Cheers, Mick. ------_=_NextPart_001_01C1309B.F088DD10 Content-Type: text/html; charset="iso-8859-1" RE: [SPIRITS] Half-Pint
I thought I would try again with this message as I realize most people were probably tied up in the IETF meetings when I sent it last.
 
In case it is not clear below, I am interested in whatever is the best way to tackle the requirements that the half-pint protocol addresses, whether that be by refining half-pint or by evolving PINT or a SPIRITS like protocol.
 
I think this clearly lines up with the goals of these groups so I'm very keen to get feedback/direction from the lists.
 
-------------------------------------------------------------------------------

The Half-Pint internet draft is now properly formatted (more or less) and available at:

http://search.ietf.org/internet-drafts/draft-odoherty-half-pint-00.txt

The idea behind the protocol is to try to provide something relatively lightweight which will still provide a useful set of services for a developer tying together web and PSTN services. The approach is to trade off flexibility and completeness for simplicity - hence the name (which is not cast in stone).

My feeling is that this protocol, while not having the same ultimate flexibility is simpler to get up and running today than a Pint/Spirits like approach, especially from the perspective of a web developer. Part of the thinking is that it is relatively well bounded and part of it is that it avoids using SIP as a transport as SIP is not quite mature enough or deployed enough today for the task - I'd be very interested to hear comments on this view - is there anyone who feels that it would be better to use SIP as the transport, maybe extending Pint ?

The main aim is to get something working quickly (say within four months as a goal) that provides the type of functionality contained in the half-pint draft and allows service developers to start their work, and that has some sort of consensus behind it from a standards point of view.

If anybody has views on this approach or on better ways to achieve the same goal, I'd be very happy to work with you to try to meet these objectives.

Cheers,

Mick.


------_=_NextPart_001_01C1309B.F088DD10-- _______________________________________________ SPIRITS mailing list SPIRITS@lists.bell-labs.com http://lists.bell-labs.com/mailman/listinfo/spirits From spirits-admin@lists.bell-labs.com Thu Aug 30 03:32:55 2001 Received: from lists.bell-labs.com (share.research.bell-labs.com [204.178.16.58]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id DAA07381 for ; Thu, 30 Aug 2001 03:32:55 -0400 (EDT) Received: from share.research.bell-labs.com (localhost.localdomain [127.0.0.1]) by lists.bell-labs.com (Postfix) with ESMTP id 0A67544356; Thu, 30 Aug 2001 02:35:04 -0400 (EDT) Delivered-To: spirits@lists.bell-labs.com Received: from obsoft.com (sdsl-208-185-238-35.dsl.sjc.megapath.net [208.185.238.35]) by lists.bell-labs.com (Postfix) with ESMTP id E0EA344336; Thu, 30 Aug 2001 02:34:42 -0400 (EDT) Received: from obsoft.com (IDENT:sardana@localhost.localdomain [127.0.0.1]) by obsoft.com (8.9.3/8.9.3) with ESMTP id AAA08720; Thu, 30 Aug 2001 00:38:26 -0700 Message-ID: <3B8DED71.AFE0EE01@obsoft.com> From: Bobby Sardana Organization: ObjectSoftware, Inc X-Mailer: Mozilla 4.61 [en] (X11; U; Linux 2.2.12-20 i686) X-Accept-Language: en MIME-Version: 1.0 To: "Michael O'Doherty" Cc: "'spirits@lists.bell-labs.com'" , pint@lists.bell-labs.com Subject: Re: [PINT] RE: [SPIRITS] Half-Pint References: Content-Type: multipart/alternative; boundary="------------7F424E352629C746C04BFC67" 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.0beta6 Precedence: bulk Reply-To: spirits@lists.bell-labs.com List-Help: List-Post: List-Subscribe: , List-Id: IETF SPIRITS Working Group List-Unsubscribe: , List-Archive: http://lists.bell-labs.com/pipermail/spirits/ Date: Thu, 30 Aug 2001 00:38:25 -0700 --------------7F424E352629C746C04BFC67 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Greetings: The draft seems interesting for PSTN service initiation. However, it follows the AVP (Attribute Value Pair) model where an action is followed by its value. You can model it like RADIUS or DIAMETER, (AAA WG) which provide definitions for AVPs and their usage, to allow addition of new actions & values. Regards, Bobby Sardana. sardana@obsoft.com Michael O'Doherty wrote: > I thought I would try again with this message as I realize most > people were probably tied up in the IETF meetings when I sent it > last.In case it is not clear below, I am interested in whatever is the > best way to tackle the requirements that the half-pint protocol > addresses, whether that be by refining half-pint or by evolving PINT > or a SPIRITS like protocol.I think this clearly lines up with the > goals of these groups so I'm very keen to get feedback/direction from > the > lists.-------------------------------------------------------------------------------The Half-Pint > internet draft is now properly formatted (more or less) and available > at: > > http://search.ietf.org/internet-drafts/draft-odoherty-half-pint-00.txt > > The idea behind the protocol is to try to provide something relatively > lightweight which will still provide a useful set of services for a > developer tying together web and PSTN services. The approach is to > trade off flexibility and completeness for simplicity - hence the name > (which is not cast in stone). > > My feeling is that this protocol, while not having the same ultimate > flexibility is simpler to get up and running today than a Pint/Spirits > like approach, especially from the perspective of a web developer. > Part of the thinking is that it is relatively well bounded and part of > it is that it avoids using SIP as a transport as SIP is not quite > mature enough or deployed enough today for the task - I'd be very > interested to hear comments on this view - is there anyone who feels > that it would be better to use SIP as the transport, maybe extending > Pint ? > > The main aim is to get something working quickly (say within four > months as a goal) that provides the type of functionality contained in > the half-pint draft and allows service developers to start their work, > and that has some sort of consensus behind it from a standards point > of view. > > If anybody has views on this approach or on better ways to achieve the > same goal, I'd be very happy to work with you to try to meet these > objectives. > > Cheers, > > Mick. --------------7F424E352629C746C04BFC67 Content-Type: text/html; charset=us-ascii Content-Transfer-Encoding: 7bit Greetings:

The draft seems interesting for PSTN service initiation. However, it follows the AVP (Attribute Value Pair) model where an action is followed by its value. You can model it like RADIUS or DIAMETER, (AAA WG) which provide definitions for AVPs and their usage, to  allow addition of new actions & values.

Regards,

Bobby Sardana.
sardana@obsoft.com

Michael O'Doherty wrote:

 I thought I would try again with this message as I realize most people were probably tied up in the IETF meetings when I sent it last.In case it is not clear below, I am interested in whatever is the best way to tackle the requirements that the half-pint protocol addresses, whether that be by refining half-pint or by evolving PINT or a SPIRITS like protocol.I think this clearly lines up with the goals of these groups so I'm very keen to get feedback/direction from the lists.-------------------------------------------------------------------------------The Half-Pint internet draft is now properly formatted (more or less) and available at:

http://search.ietf.org/internet-drafts/draft-odoherty-half-pint-00.txt

The idea behind the protocol is to try to provide something relatively lightweight which will still provide a useful set of services for a developer tying together web and PSTN services. The approach is to trade off flexibility and completeness for simplicity - hence the name (which is not cast in stone).

My feeling is that this protocol, while not having the same ultimate flexibility is simpler to get up and running today than a Pint/Spirits like approach, especially from the perspective of a web developer. Part of the thinking is that it is relatively well bounded and part of it is that it avoids using SIP as a transport as SIP is not quite mature enough or deployed enough today for the task - I'd be very interested to hear comments on this view - is there anyone who feels that it would be better to use SIP as the transport, maybe extending Pint ?

The main aim is to get something working quickly (say within four months as a goal) that provides the type of functionality contained in the half-pint draft and allows service developers to start their work, and that has some sort of consensus behind it from a standards point of view.

If anybody has views on this approach or on better ways to achieve the same goal, I'd be very happy to work with you to try to meet these objectives.

Cheers,

Mick.

--------------7F424E352629C746C04BFC67-- _______________________________________________ SPIRITS mailing list SPIRITS@lists.bell-labs.com http://lists.bell-labs.com/mailman/listinfo/spirits