IETF Logo Mail Archive

Re: Utility of Alert-Info (was: Re: [Sipping] draft-stucker-sipping-early-media-coping)

Henning Schulzrinne <hgs@cs.columbia.edu> Thu, 09 November 2006 21:18 UTC

Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1GiHHx-0006Z2-EA; Thu, 09 Nov 2006 16:18:21 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1GiHHv-0006Un-QK for sipping@ietf.org; Thu, 09 Nov 2006 16:18:19 -0500
Received: from brinza.cc.columbia.edu ([128.59.29.8]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1GiHHu-0004ZT-JD for sipping@ietf.org; Thu, 09 Nov 2006 16:18:19 -0500
Received: from [130.129.66.46] (dhcp66-46.ietf67.org [130.129.66.46]) (user=hgs10 mech=PLAIN bits=0) by brinza.cc.columbia.edu (8.13.7/8.13.6) with ESMTP id kA9LI3WH026118 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NOT); Thu, 9 Nov 2006 16:18:08 -0500 (EST)
In-Reply-To: <6FC4416DDE56C44DA0AEE67BC7CA4371116250CB@zrc2hxm2.corp.nortel.com>
References: <6FC4416DDE56C44DA0AEE67BC7CA4371116250CB@zrc2hxm2.corp.nortel.com>
Mime-Version: 1.0 (Apple Message framework v752.3)
Content-Type: text/plain; charset="US-ASCII"; delsp="yes"; format="flowed"
Message-Id: <71C12E67-507E-4D60-B72D-4018E4C271DC@cs.columbia.edu>
Content-Transfer-Encoding: 7bit
From: Henning Schulzrinne <hgs@cs.columbia.edu>
Subject: Re: Utility of Alert-Info (was: Re: [Sipping] draft-stucker-sipping-early-media-coping)
Date: Thu, 09 Nov 2006 13:18:01 -0800
To: Brian Stucker <bstucker@nortel.com>
X-Mailer: Apple Mail (2.752.3)
X-No-Spam-Score: Local
X-Scanned-By: MIMEDefang 2.48 on 128.59.29.8
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 08170828343bcf1325e4a0fb4584481c
Cc: sipping <sipping@ietf.org>
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>
Errors-To: sipping-bounces@ietf.org

I'm unclear how this could work, unless we define some global  
registry of ring tones, which seems utterly impractical.

On Nov 9, 2006, at 11:29 AM, Brian Stucker wrote:

> I would also agree.
>
> I wasn't proposing anything earlier, just stating an observed behavior
> (ala SIPit reports). I can make a recommendation in the early media
> draft though around this area.
>
> Regards,
> Brian
>


_______________________________________________
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

v2.23.0 | Report a Bug | By Email