Re: [Sip] Early media as an endpoint application

"Dwight, Timothy M (Tim)" <timothy.dwight@verizonbusiness.com> Thu, 21 August 2008 15:56 UTC

Return-Path: <sip-bounces@ietf.org>
X-Original-To: sip-archive@optimus.ietf.org
Delivered-To: ietfarch-sip-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 57FDF3A6B7A; Thu, 21 Aug 2008 08:56:52 -0700 (PDT)
X-Original-To: sip@core3.amsl.com
Delivered-To: sip@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 8B9133A6A8C for <sip@core3.amsl.com>; Thu, 21 Aug 2008 08:48:20 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level:
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 4LDoKTThJ2P8 for <sip@core3.amsl.com>; Thu, 21 Aug 2008 08:48:16 -0700 (PDT)
Received: from omzesmtp01a.verizonbusiness.com (omzesmtp01a.verizonbusiness.com [199.249.25.195]) by core3.amsl.com (Postfix) with ESMTP id 258173A6A7B for <sip@ietf.org>; Thu, 21 Aug 2008 08:48:15 -0700 (PDT)
Received: from pmismtp06.wcomnet.com ([166.37.158.166]) by firewall.verizonbusiness.com (Sun Java(tm) System Messaging Server 6.3-5.02 (built Oct 12 2007; 32bit)) with ESMTP id <0K5Y00A1YJDW8600@firewall.verizonbusiness.com> for sip@ietf.org; Thu, 21 Aug 2008 15:37:09 +0000 (GMT)
Received: from pmismtp06.wcomnet.com ([127.0.0.1]) by pmismtp06.mcilink.com (iPlanet Messaging Server 5.2 HotFix 2.08 (built Sep 22 2005)) with SMTP id <0K5Y0069FJDWON@pmismtp06.mcilink.com> for sip@ietf.org; Thu, 21 Aug 2008 15:37:09 +0000 (GMT)
Received: from ASHSRV139.mcilink.com ([153.39.68.165]) by pmismtp06.mcilink.com (iPlanet Messaging Server 5.2 HotFix 2.08 (built Sep 22 2005)) with ESMTP id <0K5Y0070IJDW93@pmismtp06.mcilink.com> for sip@ietf.org; Thu, 21 Aug 2008 15:37:08 +0000 (GMT)
Received: from ASHEVS002.mcilink.com ([153.39.71.1]) by ASHSRV139.mcilink.com with Microsoft SMTPSVC(6.0.3790.3959); Thu, 21 Aug 2008 15:37:08 +0000
Date: Thu, 21 Aug 2008 15:37:06 +0000
From: "Dwight, Timothy M (Tim)" <timothy.dwight@verizonbusiness.com>
In-reply-to: <C4D2F10C.7CB9%hsinnrei@adobe.com>
To: Henry Sinnreich <hsinnrei@adobe.com>, Dean Willis <dean.willis@softarmor.com>, Dan Wing <dwing@Cisco.COM>
Message-id: <092B2658AAB56A4D80836399A4C4703105E30A9C@ASHEVS002.mcilink.com>
MIME-version: 1.0
X-MIMEOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
Thread-topic: [Sip] Early media as an endpoint application
Thread-index: AckDoOumDEmekShGS02Y1uyPGUy4LgAAcLkA
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
References: <16BE241A-8699-485A-A450-BD27AA2EFAE6@softarmor.com> <C4D2F10C.7CB9%hsinnrei@adobe.com>
X-OriginalArrivalTime: 21 Aug 2008 15:37:08.0024 (UTC) FILETIME=[C53A1380:01C903A3]
Cc: sip@ietf.org, ekr@rtfm.com
Subject: Re: [Sip] Early media as an endpoint application
X-BeenThere: sip@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Session Initiation Protocol <sip.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/sip>, <mailto:sip-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:sip@ietf.org>
List-Help: <mailto:sip-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/sip>, <mailto:sip-request@ietf.org?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: sip-bounces@ietf.org
Errors-To: sip-bounces@ietf.org

What if you want to implement those or similar services between VoIP end
systems?  For example what if you want to provide "color ringback tones"
between VoIP end systems?  There is no PSTN gateway involvement in such
services. 

tim

> -----Original Message-----
> From: sip-bounces@ietf.org [mailto:sip-bounces@ietf.org] On 
> Behalf Of Henry Sinnreich
> Sent: Thursday, August 21, 2008 10:17 AM
> To: Dean Willis; Dan Wing
> Cc: sip@ietf.org; ekr@rtfm.com
> Subject: [Sip] Early media as an endpoint application
> 
> I have changed the Subject title
> 
> Early media should just be an endpoint application when the 
> SIP endpoint is
> a PSTN gateway. This seems logical, or does it?
> 
> ===================
> 
> I agree that early media has no role in pure/clean IP-IP 
> communications, but
> only when connecting to the PSTN. Should early media support not be
> localized in the respective SIP endpoints, that is in the 
> SIP-PSTN gateway?
> 
> Support of early media in the SIP-PSTN gateway would resolve 
> this issue.
> 
> What do you think?
> 
> Henry
> 
> 
> On 8/20/08 5:40 PM, "Dean Willis" <dean.willis@softarmor.com> wrote:
> 
> > 
> > On Aug 20, 2008, at 2:22 PM, Dan Wing wrote:
> >> 
> >> There are some apparently-legitimate uses of early media,
> > 
> > No there aren't, IMHO.
> > 
> >> at least
> >> from the perspective of some network operators, to deliver things
> >> like "Than you for using <operator>", advertisements, colorful
> >> ringback
> >> (music as ringback), and so on.  Brian did a great write-up of many
> >> scenarios in the (now expired)
> >> draft-stucker-sipping-early-media-coping-03.txt.
> > 
> > Well, if you caveat it that way., then your statement is 
> correct. One
> > might reasonably ask if those operators don't simply have their
> > requirements confused.
> > 
> > My take, however, is that "early media" is a cop-out for 
> coping with a
> > fundamentally broken PSTN-interworking model, coupled with Bad Ideas
> > about charging based on signaling rather than content.
> > 
> > But like forking, this genie has left the bottle, and we 
> have to deal
> > with the consequences of that failing as long as we have SIP 2.0.
> > 
> > ---
> > Dean
> > 
> > _______________________________________________
> > Sip mailing list  https://www.ietf.org/mailman/listinfo/sip
> > This list is for NEW development of the core SIP Protocol
> > Use sip-implementors@cs.columbia.edu for questions on current sip
> > Use sipping@ietf.org for new developments on the application of sip
> 
> _______________________________________________
> Sip mailing list  https://www.ietf.org/mailman/listinfo/sip
> This list is for NEW development of the core SIP Protocol
> Use sip-implementors@cs.columbia.edu for questions on current sip
> Use sipping@ietf.org for new developments on the application of sip
> 
_______________________________________________
Sip mailing list  https://www.ietf.org/mailman/listinfo/sip
This list is for NEW development of the core SIP Protocol
Use sip-implementors@cs.columbia.edu for questions on current sip
Use sipping@ietf.org for new developments on the application of sip