[Sipping] Re: Comment on RE: WGLC draft-ietf-sipping-callerprefs-usecases-03.txt

Paul Kyzivat <pkyzivat@cisco.com> Thu, 07 April 2005 14:04 UTC

Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA25560 for <sipping-web-archive@ietf.org>; Thu, 7 Apr 2005 10:04:23 -0400 (EDT)
Received: from megatron.ietf.org ([132.151.6.71]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1DJXkz-0003nz-C5 for sipping-web-archive@ietf.org; Thu, 07 Apr 2005 10:13:17 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1DJXav-0003Ui-Fl; Thu, 07 Apr 2005 10:02:53 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1DJXat-0003UT-Oi for sipping@megatron.ietf.org; Thu, 07 Apr 2005 10:02:52 -0400
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA25355 for <sipping@ietf.org>; Thu, 7 Apr 2005 10:02:49 -0400 (EDT)
Received: from rtp-iport-1.cisco.com ([64.102.122.148]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1DJXjR-0003iV-Nw for sipping@ietf.org; Thu, 07 Apr 2005 10:11:43 -0400
Received: from rtp-core-1.cisco.com (64.102.124.12) by rtp-iport-1.cisco.com with ESMTP; 07 Apr 2005 10:24:09 -0400
X-IronPort-AV: i="3.92,84,1112587200"; d="scan'208"; a="43523972:sNHT35760036"
Received: from flask.cisco.com (IDENT:mirapoint@flask.cisco.com [161.44.122.62]) by rtp-core-1.cisco.com (8.12.10/8.12.6) with ESMTP id j37E2U1j022939; Thu, 7 Apr 2005 10:02:31 -0400 (EDT)
Received: from cisco.com ([161.44.79.173]) by flask.cisco.com (MOS 3.4.6-GR) with ESMTP id AQK99595; Thu, 7 Apr 2005 10:02:30 -0400 (EDT)
Message-ID: <42553D75.3090909@cisco.com>
Date: Thu, 07 Apr 2005 10:02:29 -0400
From: Paul Kyzivat <pkyzivat@cisco.com>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.1) Gecko/20020826
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: "Dolly, Martin C, ALABS" <mdolly@att.com>
References: <28F05913385EAC43AF019413F674A01709F4053A@OCCLUST04EVS1.ugd.att.com>
Content-Type: text/plain; charset="us-ascii"; format="flowed"
Content-Transfer-Encoding: 7bit
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 244a2fd369eaf00ce6820a760a3de2e8
Content-Transfer-Encoding: 7bit
Cc: Rohan Mahy <rohan@ekabal.com>, Dean Willis <dean.willis@softarmor.com>, leo@cisco.com, sipping <sipping@ietf.org>, Gonzalo Camarillo <Gonzalo.Camarillo@ericsson.com>
Subject: [Sipping] Re: Comment on RE: WGLC draft-ietf-sipping-callerprefs-usecases-03.txt
X-BeenThere: sipping@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "SIPPING Working Group \(applications of SIP\)" <sipping.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sipping>, <mailto:sipping-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:sipping@ietf.org>
List-Help: <mailto:sipping-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sipping>, <mailto:sipping-request@ietf.org?subject=subscribe>
Sender: sipping-bounces@ietf.org
Errors-To: sipping-bounces@ietf.org
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 4b800b1eab964a31702fa68f1ff0e955
Content-Transfer-Encoding: 7bit

Martin,

Thanks for the feedback. A couple of questions/comments inline.

	Paul

Dolly, Martin C, ALABS wrote:
> Hello,
> 
> The use cases are well written and very clear.
> 
> It would be useful to identify dependencies in the introduction or a background section, particularly to: 
> (1) RFC 3840, Indicating User Agent Capabilities in SIP, for the new media tags, expressing capabilities in a Registration, usage of the content negotiation framework, etc..

The reference is already there in the Introduction. What more are you 
asking for?

> (2) RFC 3841, Caller Presences for the SIP, for preference and capability matching, new header definitions, etc...

I see there is screwup right now in intro. referenceing 3840 twice when 
the 2nd reference should be to 3841. Will fix that. Otherwise, what are 
you looking for?

> Lastly, the draft, along with RFC 3840/3841, describe the behavior starting at the SIP UA. And though this may be out of scope, I feel there should be something on how the user (a person) conveys their preference(s) to the SIP UA via ???. The answer maybe that this is an implementation issue.

This is a hard one. My personal opinion is that I don't expect a UA to 
provide a *general* mechanism for a user to express callerprefs for a 
call. Instead, I expect that the use of callerprefs will be implicit in 
the implementation of more coarse grained features. Exactly how that 
happens is TBD. (Example 3.19 does provide one example.)

I look on this as an introduction *to developers* of a mechanism that is 
powerful but obscure. It shows the kinds of things that are (and are 
not) possible with this mechanism. I expect actual applications to come 
later. I guess a few words can be added explaining that.

> Sorry for the delay,
> 
> Cheers,
> 
> Martin
> 
> -----Original Message-----
> From: Gonzalo Camarillo [mailto:Gonzalo.Camarillo@ericsson.com]
> Sent: Tuesday, March 01, 2005 3:03 PM
> To: sipping; Dean Willis; Rohan Mahy; Paul Kyzivat; Jonathan Rosemberg
> Cc: Cliff McCollum; Dolly, Martin C, ALABS; Chris Wang; leo@cisco.com
> Subject: WGLC draft-ietf-sipping-callerprefs-usecases-03.txt
> 
> 
> Folks,
> 
> we would like to WGLC the following draft:
> http://www.ietf.org/internet-drafts/draft-ietf-sipping-callerprefs-usecases-03.txt
> 
> This WGLC will end on March 31st.
> 
> The persons in the cc: of this email committed to perform a detailed 
> review of the draft. Once you have your review, please send it to the 
> authors and to the mailing list. Thanks a lot for volunteering.
> 
> Gonzalo
> SIPPING co-chair
> 

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