RE: [Sip] The Future of SIP Call Control

["Roy, Radhika R, ALCTA" <[e-mail]>]

Hi, Mike:

Yes, I agree with you.

Let me explain.

There needs to be a two-step process: 1. Define the SIP protocol primitives
and 2. Use of SIP protocol primitives to offer services (e.g., cc-transfer
draft).

I believe that above two-step process will ensure interoperability.

Best regards,

Radhika R. Roy
[e-mail]

-----Original Message-----
From: [e-mail] [mailto:[e-mail]]
Sent: Tuesday, November 27, 2001 5:19 PM
To: [e-mail]
Subject: Re: [Sip] The Future of SIP Call Control


In a message dated 11/27/01 1:48:03 PM Eastern Standard Time, 
[e-mail] writes:

> I think (2) is the right approach.
>  
>  We already know about a few call control primitives that we need to
>  standardize in SIP; namely, REFER and 3pcc. That work is already
underway.
>  What missing is whether that is sufficient for all call control services.
>  I'm sure its not, and I'm sure we'll also need things like the call and
>  conference state subscription work. To fully determine whats needed, I 
would
>  support a sipping item to work through some scenarios and distill out a
set
>  of required protocol primitives for supporting a range of services.
>  
>  This is not the same as standardizing those services, which I do not
>  support. 
>  
>  -Jonathan R.

I'm not sure what the distinction is between "standardizing those services" 
and the alternative. Either you do or you don't. If you don't standardize 
each service, that is, the complete protocol needed to allow it to be 
implemented on multiple devices built by multiple vendors, and to interwork 
with other services, then you can never prove interoperability and you can 
never use that service in a real network. I believe strongly that we can't 
just standardize "protocol primitives". It is first necessary to agree on
the 
set of services to be supported  and to have a concept of what "protocol 
primitives" could be, and then to determine the general way in which these 
services are to be supported in SIP. Then a set of "protocol primitives" can

be developed which provide the necessary functions, while individual 
standards are being written for each service using those "primitives".

I understand that REFER was invented as the "protocol primitive" to support 
Call Transfer, but I think I've seen it suggested for use in other places.

I see draft-ietf-sip-cc-transfer-05 is an attempt to "standardize this 
service".

Mike Pierce

_______________________________________________
Sip mailing list  http://www1.ietf.org/mailman/listinfo/sip
This list is for NEW development of the core SIP Protocol
Use [e-mail] for questions on current sip
Use [e-mail] for new developments on the application of sip

_______________________________________________
Sip mailing list  http://www1.ietf.org/mailman/listinfo/sip
This list is for NEW development of the core SIP Protocol
Use [e-mail] for questions on current sip
Use [e-mail] for new developments on the application of sip