From owner-IPTEL@lists.research.bell-labs.com  Thu Oct  1 17:43:31 1998
Received: from paperless.dnrc.bell-labs.com (paperless.dnrc.bell-labs.com [135.180.161.172])
	by ietf.org (8.8.5/8.8.7a) with ESMTP id RAA16799
	for <iptel-archive@odin.ietf.org>; Thu, 1 Oct 1998 17:43:30 -0400 (EDT)
Received: (from majordom@localhost)
	by paperless.dnrc.bell-labs.com (8.8.8/8.8.8) id LAA29096
	for iptel-outgoing; Thu, 1 Oct 1998 11:33:16 -0400 (EDT)
Message-ID: <01BDED26.1AB3C0D0@BHAMA>
From: Krishna Kurapati <kkrishna@ipcell.com>
To: "'Ami Amir'" <amir@radvision.rad.co.il>, Matt Holdrege <matt@ascend.com>
Cc: Guocai Deng <denggc@bjaimail.asiainfo.com>,
        "iptel@lists.research.bell-labs.com" <iptel@lists.research.bell-labs.com>
Subject: RE: About H.323 interoperating with ss7
Date: Thu, 1 Oct 1998 10:27:33 -0500
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: owner-iptel@lists.research.bell-labs.com
Precedence: bulk

Dear Ami,

      Thanks for the information.

      Is there a mailing-list for participating in this ITU
      activity ?

Thanks

Krishna Kurapati
IPCell Technology, Inc
2011 North Collins Blvd
Suite 707
Richardson TX 75075

(972) 671 2355

-----Original Message-----
From:	Ami Amir [SMTP:amir@radvision.rad.co.il]
Sent:	Wednesday, September 30, 1998 8:23 AM
To:	Matt Holdrege
Cc:	Guocai Deng; iptel@lists.research.bell-labs.com
Subject:	Re: About H.323 interoperating with ss7

Hi

At the last SG 16 H.323 meeting in Geneva - the IPDC documents were submitted -
and based on those inputs and discussions during the meeting, it was agreed
that a "work item" be created around the concept that gateways may be
decomposed inot two elements - High Level Control, and an assembly of media
gateways with "Low Level Control".

The concept was driven in part by the realization that in public network, SS7
or similar non-associated signaling networks, there is a need to provide a
solution where the SS7 like signaling will interface to the High Level Gateway
Control, which will then - via a high level to low level protocol - control the
media streams and gateway connections.

The plan is to work on this work item before and during the next meeting
(scheduled for November in Torino, Italy).

Ami

Matt Holdrege wrote:

> > ----------
> > From:         Matt Holdrege[SMTP:MATT@ASCEND.COM]
> > Sent:         Wednesday, September 30, 1998 1:01:54 PM
> > To:   Guocai Deng
> > Cc:   iptel@lists.research.bell-labs.com
> > Subject:      Re: About H.323 interoperating with ss7
> > Auto forwarded by a Rule
> >
> At 10:14 AM 9/30/98 +0800, Guocai Deng wrote:
> >       Who can tell me how H.323 network interoperating with SS7 network ?
> >it maybe important to support supplementary services and one stage dial.
>
> We are working on this issue in various standards bodies including the
> IETF, ITU-T, ETSI and other forums. IETF drafts include:
>
> draft-greene-ss7-arch-frame-00.txt
> draft-ong-rsgp-ss7-info-00.txt
> draft-huitema-sgcp-v1-02.txt
> draft-taylor-ipdc-00.txt
> draft-elliott-ipdc-media-00.txt
> draft-dugan-ipdc-connection-00.txt
> draft-bell-ipdc-signaling-00.txt
> draft-pickett-ipdc-management-00.txt
>
> And I'm sure we will see more before the next IETF meeting. We may see some
> new IETF working groups on this topic by then as well.
>
> ---------
> This message came from the IETF IPTEL Working Group Mailing List.



---------
This message came from the IETF IPTEL Working Group Mailing List.

---------
This message came from the IETF IPTEL Working Group Mailing List.


From owner-IPTEL@lists.research.bell-labs.com  Fri Oct  2 17:41:08 1998
Received: from paperless.dnrc.bell-labs.com (paperless.dnrc.bell-labs.com [135.180.161.172])
	by ietf.org (8.8.5/8.8.7a) with ESMTP id RAA10272
	for <iptel-archive@odin.ietf.org>; Fri, 2 Oct 1998 17:41:08 -0400 (EDT)
Received: (from majordom@localhost)
	by paperless.dnrc.bell-labs.com (8.8.8/8.8.8) id LAA01222
	for iptel-outgoing; Fri, 2 Oct 1998 11:35:16 -0400 (EDT)
From: "=?iso-8859-1?Q?G=F6ran_AP_Eriksson?=" <Goran.Eriksson@era-t.ericsson.se>
To: "Douglas Clowes" <dclowes@ozemail.com.au>,
        <iptel@lists.research.bell-labs.com>
Subject: RE: about Inter-gatekeeper operation
Date: Fri, 2 Oct 1998 17:34:18 +0200
Message-ID: <000b01bdee1a$1ea62fd0$b162d693@rcur98nbn145.ericsson.se>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3 (Normal)
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook 8.5, Build 4.71.2173.0
X-MimeOLE: Produced By Microsoft MimeOLE V4.72.2106.4
Importance: Normal
In-Reply-To: <3.0.3.32.19980928092209.00e56b70@mail.ozemail.com.au>
Sender: owner-iptel@lists.research.bell-labs.com
Precedence: bulk


Hi Douglas, cc: others.

You wrote:

Indeed, the Location Server Client Access Protocol should be encapsulated
wrt how a Location Server does its job - i.e. whether it *has* the required
information, has to go and get it, ior just invents it as it goes along. It
should be independent, as far as possible, from whether the client is a PC,
black IP phone, gateway or gatekeeper (although SIP/H.323 independence
might be more of a problem).

To put it differently, I see the Location Server being co-resident with a
Back-End-Server that (logically) provides other services, such as
authentication, authorisation, usage-recording and call-accounting. Your
view may differ.


Allowing for a situation in which the Location Server is not co-located with
the gate keeper seems appropriate. Location Management can be many things,
and solved in many ways. One should allow for that.

However, what's your view on the need to secure the communication between
the LM and the Gk?

Also, about the Back- End server; You mention that it may have several
services, such
as location management, AAA, etc? I assume that this implies different
protocols as
well, one for each service?

Regards,

G AP Eriksson
Ericsson Radio

<The content of this mail reflect my personal view only.>




---------
This message came from the IETF IPTEL Working Group Mailing List.


From owner-IPTEL@lists.research.bell-labs.com  Fri Oct  2 17:43:45 1998
Received: from paperless.dnrc.bell-labs.com (paperless.dnrc.bell-labs.com [135.180.161.172])
	by ietf.org (8.8.5/8.8.7a) with ESMTP id RAA10294
	for <iptel-archive@odin.ietf.org>; Fri, 2 Oct 1998 17:43:45 -0400 (EDT)
Received: (from majordom@localhost)
	by paperless.dnrc.bell-labs.com (8.8.8/8.8.8) id MAA01265
	for iptel-outgoing; Fri, 2 Oct 1998 12:01:16 -0400 (EDT)
Message-Id: <3.0.5.32.19981001165733.0083a600@orsmsx30>
X-Sender: jtoga@orsmsx30
X-Mailer: QUALCOMM Windows Eudora Pro Version 3.0.5 (32)
Date: Thu, 01 Oct 1998 16:57:33 -0700
To: Krishna Kurapati <kkrishna@ipcell.com>
From: Jim Toga <jim.toga@intel.com>
Subject: RE: About H.323 interoperating with ss7
Cc: iptel@lists.research.bell-labs.com
In-Reply-To: <01BDED26.1AB3C0D0@BHAMA>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Sender: owner-iptel@lists.research.bell-labs.com
Precedence: bulk

At 10:27 AM 10/1/98 -0500, you wrote:
>Dear Ami,
>
>      Thanks for the information.
>
>      Is there a mailing-list for participating in this ITU
>      activity ?
>
>Thanks
>
>Krishna Kurapati
>IPCell Technology, Inc
>2011 North Collins Blvd
>Suite 707
>Richardson TX 75075
>
>(972) 671 2355
>
>-----Original Message-----
>From:	Ami Amir [SMTP:amir@radvision.rad.co.il]
>Sent:	Wednesday, September 30, 1998 8:23 AM
>To:	Matt Holdrege
>Cc:	Guocai Deng; iptel@lists.research.bell-labs.com
>Subject:	Re: About H.323 interoperating with ss7
>
>Hi
>
>At the last SG 16 H.323 meeting in Geneva - the IPDC documents were
submitted -
>and based on those inputs and discussions during the meeting, it was agreed
>that a "work item" be created around the concept that gateways may be
>decomposed inot two elements - High Level Control, and an assembly of media
>gateways with "Low Level Control".
>
>The concept was driven in part by the realization that in public network, SS7
>or similar non-associated signaling networks, there is a need to provide a
>solution where the SS7 like signaling will interface to the High Level
Gateway
>Control, which will then - via a high level to low level protocol -
control the
>media streams and gateway connections.
>
>The plan is to work on this work item before and during the next meeting
>(scheduled for November in Torino, Italy).
>
>Ami
>
>
>
>---------
>This message came from the IETF IPTEL Working Group Mailing List.
>
>---------
>This message came from the IETF IPTEL Working Group Mailing List.
>
To Subscribe to the list send email to:
	
	listserv@mailbag.cps.intel.com
with the body of the message set to:

	subscribe itu-sg16 [your name]

(note that your email address will be picked up from the header of the
message)


Remember - to POST messages to the list send to:

                itu-sg16@mailbag.cps.intel.com

Note that 'reply' to the message will be sent back to the list, NOT the
original author of the message.  If you want to reply directly and only to
the sender of a message you must fix the return address.

jimt.


*****************************************************
***  +1-503-264-8816(voice)              Intel - Hillsboro, OR.
    *** 
***  mailto:jim.toga@intel.com         mailto:james.toga@ties.itu.int *** 
***  PGP keyID 36 07 86 49 7D 74 DF 57  50 CB BA 32 08 9C 7C 41 ***
*****************************************************
---------
This message came from the IETF IPTEL Working Group Mailing List.


From owner-IPTEL@lists.research.bell-labs.com  Fri Oct  9 10:11:36 1998
Received: from paperless.dnrc.bell-labs.com (paperless.dnrc.bell-labs.com [135.180.161.172])
	by ietf.org (8.8.5/8.8.7a) with ESMTP id KAA27632
	for <iptel-archive@odin.ietf.org>; Fri, 9 Oct 1998 10:11:36 -0400 (EDT)
Received: (from majordom@localhost)
	by paperless.dnrc.bell-labs.com (8.8.8/8.8.8) id EAA02010
	for iptel-outgoing; Fri, 9 Oct 1998 04:39:16 -0400 (EDT)
Message-ID: <004601bdf360$5ac7dea0$060a060a@dream.ritt.org.cn>
Reply-To: "rick king" <rickyy@bbs.huizhou.gd.cn>
From: "rick king" <rickyy@bbs.huizhou.gd.cn>
To: "Guo, Liang" <guol@ccs.neu.edu>
Cc: "iptel" <iptel@lists.research.bell-labs.com>,
        "mpls" <mpls@netlab.indiana.edu>
Subject: =?gb2312?B?u9i4tDogYWJvdXQgUW9T?=
Date: Fri, 9 Oct 1998 16:39:38 +0800
MIME-Version: 1.0
Content-Type: text/plain;
	charset="gb2312"
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 4.72.3110.5
X-MimeOLE: Produced By Microsoft MimeOLE V4.72.3110.3
Sender: owner-iptel@lists.research.bell-labs.com
Precedence: bulk

>
>It's a good idea, but it has already been implemented in classic IP,
>it's called "TOS(type of service" field.

It's defined,but isn't be implemented,as many guys say.
>
>Now the problem is to provide more than that, so we have to deal with
>the "quality" of the path so as to find a path that has enough
If everyone want to find this kind of path,there will be too many paths.:<
And it will be like ATM and circuit switch.
>bandwidth, bounded delay and so on, which can not be solved
>by this simple method.



---------
This message came from the IETF IPTEL Working Group Mailing List.


From owner-IPTEL@lists.research.bell-labs.com  Fri Oct  9 10:29:11 1998
Received: from paperless.dnrc.bell-labs.com (paperless.dnrc.bell-labs.com [135.180.161.172])
	by ietf.org (8.8.5/8.8.7a) with ESMTP id KAA28110
	for <iptel-archive@odin.ietf.org>; Fri, 9 Oct 1998 10:29:10 -0400 (EDT)
Received: (from majordom@localhost)
	by paperless.dnrc.bell-labs.com (8.8.8/8.8.8) id EAA02000
	for iptel-outgoing; Fri, 9 Oct 1998 04:29:16 -0400 (EDT)
Message-ID: <003801bdf35e$c4888a80$060a060a@dream.ritt.org.cn>
Reply-To: "rick king" <rickyy@bbs.huizhou.gd.cn>
From: "rick king" <rickyy@bbs.huizhou.gd.cn>
To: "mpls" <mpls@netlab.indiana.edu>
Cc: "iptel" <iptel@lists.research.bell-labs.com>
Subject: =?gb2312?B?u9i4tDogYWJvdXQgUW9T?=
Date: Fri, 9 Oct 1998 16:28:12 +0800
MIME-Version: 1.0
Content-Type: text/plain;
	charset="gb2312"
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 4.72.3110.5
X-MimeOLE: Produced By Microsoft MimeOLE V4.72.3110.3
Sender: owner-iptel@lists.research.bell-labs.com
Precedence: bulk

>hai,
>The reasons can be:
>IPv4 has TOS bit. But most of the current implementations ignore
>that bit. ( I think it is same ( to some extent ) ur proposal.
yes,I know the TOS bit.I think the reason that current implementations
ignore TOS bits is:
1)The classic IP software like telnet,ftp,web brower don't need QoS, so
these days  router doesn't support the TOS bits.
2)If you want to support ToS,then you need to bill the consumer by the TOS
he applying.Many people maybe don't like this before.But now as IP phone
appear,I think someone will like to pay for it.


>1. If u have only bit then u can't support different classes of QoS.
you are right,I only take it as example.
>2. RSVP and MPLS are not just not ment for QoS but Multicast QoS
>service.
>( I mean they provide mechanisms to support such stuff)
So it's still a kind of QoS..:)
>3. Treating all the classes the same, other than the best effort
>traffic is not a good n/w design.
> 4. Why do u think RSVP  implementation is diffcult. I think some body
>a good implementation. I remember that somebody mentioned about their
> implementation in this mailing list. ( I agree that deployment in the
>current interner is diffcult..)
As I know RSVP need some routing protocol to support it,maybe MPLS is a good
choice. I am expect them too..
> 5. If you want to support IP telephony kind of applications
> we need RSVP.
maybe,but there is diffserv now..*_^
>
>Correct me If I am wrong.
>
>Thanks
>-Raghu.
>
>

---------
This message came from the IETF IPTEL Working Group Mailing List.


From owner-IPTEL@lists.research.bell-labs.com  Fri Oct  9 13:50:38 1998
Received: from paperless.dnrc.bell-labs.com (paperless.dnrc.bell-labs.com [135.180.161.172])
	by ietf.org (8.8.5/8.8.7a) with ESMTP id NAA04156
	for <iptel-archive@odin.ietf.org>; Fri, 9 Oct 1998 13:50:38 -0400 (EDT)
Received: (from majordom@localhost)
	by paperless.dnrc.bell-labs.com (8.8.8/8.8.8) id HAA02109
	for iptel-outgoing; Fri, 9 Oct 1998 07:07:16 -0400 (EDT)
Message-Id: <361DEE47.3EE058AB@hpl.hp.com>
Date: Fri, 09 Oct 1998 12:06:48 +0100
From: Claudio Catania <cld@hplb.hpl.hp.com>
Reply-To: Claudio Catania <cld@hplb.hpl.hp.com>
Organization: Hewlett Packard laboratories
X-Mailer: Mozilla 4.05 [en] (WinNT; I)
Mime-Version: 1.0
To: iptel@lists.research.bell-labs.com
Subject: Few comments on requirements for CPL
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Sender: owner-iptel@lists.research.bell-labs.com
Precedence: bulk

Hello,

From the minutes of the last IETF meeting, I got the impression that CPL
was a hot topic but, due to lack of time,  there had been several
unanswered questions about the slide set that J.Lennox presented.

I am struggling to understand what people in the mailing list think
about the requirements and what the status of this activity is.

 Recently I browsed through my Iptel archive and found  very few
comments about the CPL requirements draft.

Several questions came to my mind, I will try to summarize some of them
here, hoping that someone could help expanding on them.

1)
One of the things that could be achieved by CPL is the definition of a
controlled environment to create services on a "network device". This
seems to be very similar to the approach taken by IN community when they
tried to define SCEs for IN components.
*Does anyone have an opinion on how CPL could be related to those
efforts?

2)
I think that, after having spent several years trying to define good
controlled service creation environments for basic reliable services,
the IN community is struggling to enhance their simple model to add
distribution, flexibility and efficient
communication between network elements. Services for VoIP may have
completely different requirements but, at the end of the day,  we are
talking about server based call processing languages, therefore there
may be  a lot of similarities.
*Is CPL in a better position to address the issue of combining
flexibility with controlled environment for service creation?

3)
My understanding is that CPL proposes to run up to four different
scripts every time a service  is invoked (user and administrator scripts
for both originating  and destination party).  VoIP client and server
providers will have to ensure compatibility between them all. Now it is
very likely that the former will try to sell their own administrative
tools to configure and remote administer their clients while the latter
will probably be reluctant  to share a common service environment (I
could be wrong, but I think that this is exactly what happened to  IN
SCEs and service languages).
*Who would really benefit from a standardized way of writing services in
CPL?
*How will VoIP client and server providers deal with potential conflicts
between scripts running on different environment? (I guess that the
draft identifies these problems and calls them server to server
interactions;  I could not figure out how the problem is solved.)

4)
According to the draft, CPL can be implemented in several languages (see
the requirements), but I got the impression that the adopted one will be
XML.
*Why? Is there a compelling reason for which XML should be used? Are the
reasons mentioned in the draft good enough?
*What is good in using XML for services?

5)
A service based on a call processing language have to be mainly stateful
and event driven (the draft mentioned a few non stateless service
scenarios)
*Why is a "non-expressively-complete scripting language" the best
solution for that?

6)
My understanding is that approaches based on a expressively-complete
languages (TAPI, old TSAPI...) successfully hide the call processing
coming from different signalling stacks. There had been several attempts
to standardize those solutions but no one reached global consensus. I
guess that this happened  mainly because vendors did not want to open
their platforms thus providing the aprropriate drivers for standardized
environments.
*If  CPL has the same requirements, will VoIP server vendors behave in a
different way and open up their APIs to CPL?

I apologize for such a long mail

Claudio Catania




--
----------------------------------------------------------
 Claudio Catania  Senior Research engineer
 mailto:cld@hpl.hp.com    Hewlett-Packard Laboratories
 Phone: +44 117 922 8235
 Fax:   +44 117 922 8003     Filton Road, Stoke Gifford
 Telnet: 312 8235            Bristol (U.K.)  BS34 8QZ
----------------------------------------------------------


---------
This message came from the IETF IPTEL Working Group Mailing List.


From owner-IPTEL@lists.research.bell-labs.com  Fri Oct 23 23:53:50 1998
Received: from paperless.dnrc.bell-labs.com (paperless.dnrc.bell-labs.com [135.180.161.172])
	by ietf.org (8.8.5/8.8.7a) with ESMTP id XAA18485
	for <iptel-archive@odin.ietf.org>; Fri, 23 Oct 1998 23:53:49 -0400 (EDT)
Received: (from majordom@localhost)
	by paperless.dnrc.bell-labs.com (8.8.8/8.8.8) id RAA02278
	for iptel-outgoing; Fri, 23 Oct 1998 17:56:02 -0400 (EDT)
Message-ID: <3630FACF.D17EFC62@dnrc.bell-labs.com>
Date: Fri, 23 Oct 1998 17:53:19 -0400
From: Jonathan Rosenberg <jdrosen@dnrc.bell-labs.com>
X-Mailer: Mozilla 4.04 [en] (WinNT; I)
MIME-Version: 1.0
To: Claudio Catania <cld@hplb.hpl.hp.com>
CC: iptel@lists.research.bell-labs.com
Subject: Re: Few comments on requirements for CPL
References: <361DEE47.3EE058AB@hpl.hp.com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Sender: owner-iptel@lists.research.bell-labs.com
Precedence: bulk

Claudio Catania wrote:
> 
> Hello,
> 
> >From the minutes of the last IETF meeting, I got the impression that CPL
> was a hot topic but, due to lack of time,  there had been several
> unanswered questions about the slide set that J.Lennox presented.
> 
> I am struggling to understand what people in the mailing list think
> about the requirements and what the status of this activity is.
> 
>  Recently I browsed through my Iptel archive and found  very few
> comments about the CPL requirements draft.

Right now the group is "focusing" on getting the gateway location
framework document out. Most of the discussion has centered around this,
rather than the CPL stuff.

> 
> Several questions came to my mind, I will try to summarize some of them
> here, hoping that someone could help expanding on them.
> 
> 1)
> One of the things that could be achieved by CPL is the definition of a
> controlled environment to create services on a "network device". This
> seems to be very similar to the approach taken by IN community when they
> tried to define SCEs for IN components.
> *Does anyone have an opinion on how CPL could be related to those
> efforts?

I'm really not that familiar with the SCE's in IN components. My
understanding (and please correct if I'm mistaken) is that these are
interfaces and tools for linking together objects, events, and actions
to define services. They are used primarily by network administrators.
In my mind, the CPL is not meant to be a complete and fully specified
tool to define all possible services. I think the focus should be on a
language that exposes certain services to end users. This, as a result,
generates the requirements for safety, simplicity, and ease of use and
generation. This doesn't mean that a CPL couldn't be used by an
administrator to define new services, but that it is engineered to be
created by end users. This, I think, means it is not (nor should it be)
a complete environment for truly flexible service creation. It should
expose a limited and controlled set of options and features to an end
user, but no more.

However, we could certainly learn from the SCE efforts, and I would
encourage drafts/email on the subject.


> 
> 2)
> I think that, after having spent several years trying to define good
> controlled service creation environments for basic reliable services,
> the IN community is struggling to enhance their simple model to add
> distribution, flexibility and efficient
> communication between network elements. Services for VoIP may have
> completely different requirements but, at the end of the day,  we are
> talking about server based call processing languages, therefore there
> may be  a lot of similarities.
> *Is CPL in a better position to address the issue of combining
> flexibility with controlled environment for service creation?

As I mention above, I don't think its meant to encompass the breadth
provided by IN SCE's, but I'd welcome discussion if people believe
otherwise.

> 
> 3)
> My understanding is that CPL proposes to run up to four different
> scripts every time a service  is invoked (user and administrator scripts
> for both originating  and destination party).

No, there is no such limit. There may be many scripts which run. 

  VoIP client and server
> providers will have to ensure compatibility between them all. Now it is
> very likely that the former will try to sell their own administrative
> tools to configure and remote administer their clients while the latter
> will probably be reluctant  to share a common service environment (I
> could be wrong, but I think that this is exactly what happened to  IN
> SCEs and service languages).
> *Who would really benefit from a standardized way of writing services in
> CPL?

End users. These scripts would be standardized ways for end users to
"configure", in a limited sense, servers, and possibly clients. I do not
think that the CPL will be an effective tool for service providers to
configure servers, but they would be welcome to do so if it fits their
needs.

> *How will VoIP client and server providers deal with potential conflicts
> between scripts running on different environment? (I guess that the
> draft identifies these problems and calls them server to server
> interactions;  I could not figure out how the problem is solved.)

Could you clarify exactly which aspects of the problem didn't seem
resolved in the draft?

> 
> 4)
> According to the draft, CPL can be implemented in several languages (see
> the requirements), but I got the impression that the adopted one will be
> XML.
> *Why? Is there a compelling reason for which XML should be used? Are the
> reasons mentioned in the draft good enough?
> *What is good in using XML for services?

The original idea was to possibly use something like Tcl. However, XML
has some compelling features. Safety is the main issue with the CPL -
since the focus is on generation by end users and execution in network
servers, the providers must be sure that the scripts will terminate, and
can't do malicious things. We also wanted to be able to make sure the
script was syntactically and semantically correct. XML is nice in this
regard - we can define a restricted set of keywords, and the script is
in a highly structured, easily parsable and verifiable format. Its
hardly a programming language at all - but I think thats what we want.
Its also easily extended with new keywords using standard XML
mechanisms.

XML has its drawbacks - its nested structure makes specification of some
services fairly ugly. Its structure also makes a lot of standard
programming constructs complex - but one can argue that this is a good
thing. Again, we're not looking for a full blown language/API here -
just a syntax an end user can upload to specify some basic services.


> 
> 5)
> A service based on a call processing language have to be mainly stateful
> and event driven (the draft mentioned a few non stateless service
> scenarios)
> *Why is a "non-expressively-complete scripting language" the best
> solution for that?

Again, I think its related to the environment we're considering -
generation by end users.

> 
> 6)
> My understanding is that approaches based on a expressively-complete
> languages (TAPI, old TSAPI...) successfully hide the call processing
> coming from different signalling stacks. There had been several attempts
> to standardize those solutions but no one reached global consensus. I
> guess that this happened  mainly because vendors did not want to open
> their platforms thus providing the aprropriate drivers for standardized
> environments.
> *If  CPL has the same requirements, will VoIP server vendors behave in a
> different way and open up their APIs to CPL?

I think the amount of "opening" we're talking about here is quite a bit
less than TAPI and TSAPI. There are definitely examples of where service
providers in the IP world have made network services available to end
users - CGI scripts, .forward files, both expose aspects of web and
email services to end users. Whether the CPL will be successful or not,
only time will tell.

-Jonathan R.

-- 
Jonathan D. Rosenberg                       Lucent Technologies
Member of Technical Staff                   101 Crawfords Corner Rd.
High Speed Networks Research                Holmdel, NJ 07733
FAX:   (732) 834-5379                       Rm. 4C-526
EMAIL: jdrosen@bell-labs.com
URL: http://www.cs.columbia.edu/~jdrosen
---------
This message came from the IETF IPTEL Working Group Mailing List.


From owner-IPTEL@lists.research.bell-labs.com  Thu Oct 29 01:00:03 1998
Received: from paperless.dnrc.bell-labs.com (paperless.dnrc.bell-labs.com [135.180.161.172])
	by ietf.org (8.8.5/8.8.7a) with ESMTP id BAA28668
	for <iptel-archive@odin.ietf.org>; Thu, 29 Oct 1998 01:00:03 -0500 (EST)
Received: (from majordom@localhost)
	by paperless.dnrc.bell-labs.com (8.8.8/8.8.8) id TAA12695
	for iptel-outgoing; Wed, 28 Oct 1998 19:14:37 -0500 (EST)
Message-ID: <3637B2B5.875892CE@dnrc.bell-labs.com>
Date: Wed, 28 Oct 1998 19:11:33 -0500
From: Jonathan Rosenberg <jdrosen@dnrc.bell-labs.com>
X-Mailer: Mozilla 4.04 [en] (WinNT; I)
MIME-Version: 1.0
To: list iptel <iptel@lists.research.bell-labs.com>
Subject: Updated draft
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Sender: owner-iptel@lists.research.bell-labs.com
Precedence: bulk

Folks,

I've just submitted an updated framework document to the archives. Until
it appears, you can pick up a copy at:

http://www.cs.columbia.edu/~jdrosen/papers/draft-ietf-iptel-gwloc-framework-01.txt

The document incorporates the decisions reached at the last IETF
meeting. It also includes some consensus from the list afterwards
(namely, that a location server and gatekeeper/SIP server need not be
coresident). Theres still a bunch of open issues. The main ones are
aggregation, attributes, and what Christian called path qualification.
I'd like to hear discussion on these, and comments on the draft in
general.

I'd also like to incorporate comments from the list between now and the
meeting and submit another update before the Nov 18th draft deadline.
We'll then have a chance at 1 more revision after the meeting if we want
to meet the Jan 99 deadline for last call for the framework.

Thanks,
Jonathan R.
-- 
Jonathan D. Rosenberg                       Lucent Technologies
Member of Technical Staff                   101 Crawfords Corner Rd.
High Speed Networks Research                Holmdel, NJ 07733
FAX:   (732) 834-5379                       Rm. 4C-526
EMAIL: jdrosen@bell-labs.com
URL: http://www.cs.columbia.edu/~jdrosen
---------
This message came from the IETF IPTEL Working Group Mailing List.


From owner-IPTEL@lists.research.bell-labs.com  Fri Oct 30 01:37:05 1998
Received: from paperless.dnrc.bell-labs.com (paperless.dnrc.bell-labs.com [135.180.161.172])
	by ietf.org (8.8.5/8.8.7a) with ESMTP id BAA20738
	for <iptel-archive@odin.ietf.org>; Fri, 30 Oct 1998 01:37:05 -0500 (EST)
Received: (from majordom@localhost)
	by paperless.dnrc.bell-labs.com (8.8.8/8.8.8) id TAA14751
	for iptel-outgoing; Thu, 29 Oct 1998 19:39:15 -0500 (EST)
From: "Karen Goettler" <kgoettler@peakss.com>
Cc: <iptel@lists.research.bell-labs.com>
Subject: RE: Few comments on requirements for CPL
Date: Thu, 29 Oct 1998 17:37:56 -0700
Message-ID: <007601be039d$89ba7680$69001cac@tweety.peakss.com>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3 (Normal)
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook 8.5, Build 4.71.2377.0
Importance: Normal
X-MimeOLE: Produced By Microsoft MimeOLE V4.72.2120.0
In-Reply-To: <3630FACF.D17EFC62@dnrc.bell-labs.com>
Sender: owner-iptel@lists.research.bell-labs.com
Precedence: bulk

I teach an 'IN Networks and Services' class at a local university and have
been wondering, since you are talking about VoIP Services and the VoIP CLP,
'How are VoIP services triggered?'.

It seems like the services should be triggered as part of the CPL, but does
the CPL for VoIP have defined states where services could be triggered?
Also, where will the CPL run, on the end device or at a centralized location
on the network?  Is the idea to use a model like wireless telephony where
all of a users' service information is stored in a central network location
(the HLR)?

-----------------------------------------------------
Karen Goettler
phone - 303 734-5015
fax   - 303 734-4244
kgoettler@peakss.com

PEAK Software Solutions, Inc.
7851 S Elati Street, Suite 200 Littleton, CO  80120
-----------------------------------------------------

---------
This message came from the IETF IPTEL Working Group Mailing List.


From owner-IPTEL@lists.research.bell-labs.com  Sat Oct 31 21:23:39 1998
Received: from paperless.dnrc.bell-labs.com (paperless.dnrc.bell-labs.com [135.180.161.172])
	by ietf.org (8.8.5/8.8.7a) with ESMTP id VAA14424
	for <iptel-archive@odin.ietf.org>; Sat, 31 Oct 1998 21:23:39 -0500 (EST)
Received: (from majordom@localhost)
	by paperless.dnrc.bell-labs.com (8.8.8/8.8.8) id PAA18202
	for iptel-outgoing; Sat, 31 Oct 1998 15:37:26 -0500 (EST)
From: scj2@gs4.revnet.com
Message-Id: <199810312034.OAA30963@revnet4.revnet.com>
To: scj2@gs4.revnet.com
Subject: ISM Corp has acquired 4.7 mill to begin production Stock up 100 percent
Date: Sat, 31 Oct 1998 14:39:04 -0600
Originator: scj2@gs4.revnet.com
X-Mailer: GroupMaster
X-Mailer-Version: 1.5
X-GroupMasterUser: Revnet Express
Sender: owner-iptel@lists.research.bell-labs.com
Precedence: bulk


Please open the following message in your web browser

    http://gs4.revnet.com/GM/MSGVIEW/MSOHNOPA.HTML
____________________________________________________________
International Shoe Manufacturing Corp Update: 
International Shoe Manufacturing Corp. (Ticker-ISHO) has acquired the final-stage
financing to begin full-scale production at its plants in India. The $4.75 million is being
used to purchase the final equipment needed to begin production at the company’s existing
plant in India. With equipment in place, the company projects net profits of over $25
million a year within two years.

The company stated that the financing will be followed up by a $9 million dollar IPO in
India, anticipated for March 1999. The IPO will be handled by underwriters in India, and
will leave ISM with control of its wholly owned subsidiary in India. The proceeds of the
IPO will pay off the $4.75 million dollar financing. The balance will be used for the
acquisition of additional shoe manufacturing.    

ISHO is in the business of manufacturing athletic footwear for the world’s leading shoe
companies. It owns a 23,000-square-foot plant located in the protected “free trade zone” in
Noida, just outside of New Delhi, India, where skilled labor is plentiful and very
inexpensive. The Indian government recently developed new economic policy to attract
foreign investment that is export-oriented, and could employ large numbers of people. 
ISM is the only athletic shoe manufacturer in India directed toward the international
market. It currently has contracts with Adidas and The Pentland Group. These two
companies have agreed to purchase all the shoes ISM can manufacture. 

The athletic shoe industry is estimated at $14.25 billion a year. The world’s leading shoe
companies such as Adidas, Nike, and Reebok do not manufacture shoes. They are design
and marketing organizations that spend hundreds of millions of dollars a year getting their
products sold. They then rely on others to manufacture to their specifications. Almost, if
not all athletic shoe manufacturers are privately owned, benefiting from the hundreds of
millions of dollars spent on advertising by the name-brand companies. The result is an
open purchase order where such manufacturers  literally can sell every pair of shoes they
can produce. A business like this lends itself to being privately held due to the large cash
flow allowing for internal financing. International Shoe Manufacturing Corp. is the only
company known to exist that offers a public investor the opportunity to own a share of this
highly lucrative business in a pure  investment play.

For inquiries please contact the office of the director of investor relations toll free at: 
877-ISM-CORP  (877-476-2677)  or send your e-mail request to nsi@smallcapjournal.com Your request will be handled immediately.  Or write to ISM Corp at P.O. Box 520310 Longwood, Florida 32752

Please visit ISM’s web site at www.ismcorp.net
Safe Harbor for Forward-Looking Statements: Except for historical information contained herein, the statements in this press
release are forward-looking statements that are made pursuant to the safe harbor provisions of the Private Securities Reform Act of
1995.  Forward-looking statements involve known and unknown risks and uncertainties which may cause the company’s actual
results in the future periods to differ materially from forecasted results. These risks and uncertainties include, among other things,
product price volatility, product demand, market competition, risk inherent in the company’s domestic and international operations,
imprecision in estimating product reserves and the company’s ability to replace and expand its holdings.

____________________________________________________________

Unsubscribe or access your membership settings at: 
http://gs4.revnet.com/GMG/ctrlpanel/0/79
---------
This message came from the IETF IPTEL Working Group Mailing List.


