Re: [Sipping] I-D on service identification now available

[Bruce Qi <qibj at huawei.com>]

Hi Jonathan and All ,
      The draft is really great!   The draft describes many problem that we are discussing .
 
About "egotiation of Service",I  think that something need to be clarified.

5.6.  Negotiation of Service

   In some cases, when the caller initiates a session, they don't
   actually know which service will be utilized.  Rather, they might
   like to offer up all of the services they have available to the
   called party, and then let the called party decide, or let the system
   make a decision based on overlapping service capabilities.

   As an example, s user can do both the game and the voice chat service
   of Section 4.2.  They initiate a session to a target AOR, but the
   devices used by that user can only support voice chat.  Consequently,
   voice chat gets utilized for the session.

1)  When the called party or the system decide the sevice that this session will invoke,  should the caller know the invoked sevice? Maybe the sip response message includes the infomation about the invoked service .
2)  There is the other case about "negotiation of service", For example , the initial request includes the  two or more service identifiers. when the called party or the system receives the request, they may decide which one service will be invoked.  I think the cases of " negotiation of service " should include this case.


Thinks 
Bruce Qi


----- Original Message ----- 
From: "Jonathan Rosenberg" <jdrosen at cisco.com>
To: "IETF Sipping List" <sipping at ietf.org>
Sent: Tuesday, May 08, 2007 12:42 AM
Subject: [Sipping] I-D on service identification now available


> During the Prague IETF, we discussed producing a document that is an 
> expository on the architectural principles behind service identification 
> - what it means, why people want it, what the perils are. I've now 
> finished this, and posted it. Until it appears, you can pick it up here:
> 
> http://www.jdrosen.net/papers/draft-rosenberg-sipping-service-identification-02.txt
> 
> This is a complete rewrite of the previous document, following the 
> outline I proposed in Prague.
> 
> Thanks,
> Jonathan R.
> -- 
> Jonathan D. Rosenberg, Ph.D.                   600 Lanidex Plaza
> Cisco Fellow                                   Parsippany, NJ 07054-2711
> Cisco Systems
> jdrosen at cisco.com                              FAX:   (973) 952-5050
> http://www.jdrosen.net                         PHONE: (973) 952-5000
> http://www.cisco.com
> 
> 
> _______________________________________________
> Sipping mailing list  https://www1.ietf.org/mailman/listinfo/sipping
> This list is for NEW development of the application of SIP
> Use sip-implementors at cs.columbia.edu for questions on current sip
> Use sip at ietf.org for new developments of core SIP
>


_______________________________________________
Sipping mailing list  https://www1.ietf.org/mailman/listinfo/sipping
This list is for NEW development of the application of SIP
Use sip-implementors at cs.columbia.edu for questions on current sip
Use sip at ietf.org for new developments of core SIP