Re: Last Call comment: draft-rosenberg-sip-app-media-tag-01.txt

Ted Hardie <hardie@qualcomm.com> Wed, 25 July 2007 15:01 UTC

Return-path: <discuss-bounces@apps.ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1IDiMU-0007f1-3K; Wed, 25 Jul 2007 11:01:14 -0400
Received: from discuss by megatron.ietf.org with local (Exim 4.43) id 1IDiMS-0007ei-4Y for discuss-confirm+ok@megatron.ietf.org; Wed, 25 Jul 2007 11:01:12 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1IDiMR-0007ea-R8 for discuss@apps.ietf.org; Wed, 25 Jul 2007 11:01:11 -0400
Received: from ithilien.qualcomm.com ([129.46.51.59]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1IDiMQ-0000pi-Cn for discuss@apps.ietf.org; Wed, 25 Jul 2007 11:01:11 -0400
Received: from hamtaro.qualcomm.com (hamtaro.qualcomm.com [129.46.61.157]) by ithilien.qualcomm.com (8.13.6/8.12.5/1.0) with ESMTP id l6PF18ph023309 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=FAIL); Wed, 25 Jul 2007 08:01:09 -0700
Received: from [130.129.17.237] (vpn-10-50-16-124.qualcomm.com [10.50.16.124]) by hamtaro.qualcomm.com (8.13.6/8.13.6/1.0) with ESMTP id l6PF16cw029640; Wed, 25 Jul 2007 08:01:07 -0700 (PDT)
Mime-Version: 1.0
Message-Id: <p06240604c2cd1561027b@[130.129.17.237]>
In-Reply-To: <46A76314.4040103@dcrocker.net>
References: <p06240602c2cc3be27967@[130.129.20.116]> <46A76314.4040103@dcrocker.net>
Date: Wed, 25 Jul 2007 10:01:09 -0500
To: dcrocker@bbiw.net
From: Ted Hardie <hardie@qualcomm.com>
Subject: Re: Last Call comment: draft-rosenberg-sip-app-media-tag-01.txt
Content-Type: text/plain; charset="us-ascii"
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 9182cfff02fae4f1b6e9349e01d62f32
Cc: discuss@apps.ietf.org, Dave Crocker <dhc2@dcrocker.net>, ietf@ietf.org
X-BeenThere: discuss@apps.ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: general discussion of application-layer protocols <discuss.apps.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/discuss>, <mailto:discuss-request@apps.ietf.org?subject=unsubscribe>
List-Post: <mailto:discuss@apps.ietf.org>
List-Help: <mailto:discuss-request@apps.ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/discuss>, <mailto:discuss-request@apps.ietf.org?subject=subscribe>
Errors-To: discuss-bounces@apps.ietf.org

At 9:49 AM -0500 7/25/07, Dave Crocker wrote:
>Ted Hardie wrote:
>>      A broader solution that encompasses other potential
>>uses of content negotiation seems to me in order. 
>
>Other than probably looking for an interaction mechanism, rather than one through email, does this have any relationship to:
>
>   Content Negotiation for Messaging Services based on Email
>   <http://www.apps.ietf.org/rfc/rfc3297.html>?
>
>d/
>--
>
>  Dave Crocker
>  Brandenburg InternetWorking
>  bbiw.net

The SIP preference/capabilities work broadly re-uses the CONNEG framework.

This optimization treats a particular problem with "application" as a top-level
type in the SIP context.  Though there are application types in 3297 (application/pdf),
using them in negotiation hits SIP in somewhat different ways.  The question is
whether generalizing the subtype  content negotiation needed there would be
useful for other content negotiation users.
				Ted