[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [Sip] Some comments on draft-ietf-sip-dtls-srtp-framework-02
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 at 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 yFrom sip-bounces at ietf.org Thu Aug 21 12:44:52 2008
Return-Path: <sip-bounces at ietf.org>
X-Original-To: sip-archive at optimus.ietf.org
Delivered-To: ietfarch-sip-archive at core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
by core3.amsl.com (Postfix) with ESMTP id 82E783A69A7;
Thu, 21 Aug 2008 12:44:52 -0700 (PDT)
X-Original-To: sip at core3.amsl.com
Delivered-To: sip at core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
by core3.amsl.com (Postfix) with ESMTP id 0A5163A69A7
for <sip at core3.amsl.com>; Thu, 21 Aug 2008 12:44:51 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.599
X-Spam-Level:
X-Spam-Status: No, score=-6.599 tagged_above=-999 required=5
tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
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 HgGn7tifwGLH for <sip at core3.amsl.com>;
Thu, 21 Aug 2008 12:44:50 -0700 (PDT)
Received: from exprod6og114.obsmtp.com (exprod6og114.obsmtp.com [64.18.1.33])
by core3.amsl.com (Postfix) with ESMTP id A86F63A6783
for <sip at ietf.org>; Thu, 21 Aug 2008 12:44:49 -0700 (PDT)
Received: from source ([192.150.8.22]) by exprod6ob114.postini.com
([64.18.5.12]) with SMTP; Thu, 21 Aug 2008 12:43:55 PDT
Received: from inner-relay-1.corp.adobe.com ([153.32.1.51])
by outbound-smtp-2.corp.adobe.com (8.12.10/8.12.10) with ESMTP id
m7LDxLE0005848; Thu, 21 Aug 2008 06:59:22 -0700 (PDT)
Received: from fe2.corp.adobe.com (fe2.corp.adobe.com [10.8.192.72])
by inner-relay-1.corp.adobe.com (8.12.10/8.12.10) with ESMTP id
m7LDxGiq018910; Thu, 21 Aug 2008 06:59:16 -0700 (PDT)
Received: from namail5.corp.adobe.com ([10.8.192.88]) by fe2.corp.adobe.com
with Microsoft SMTPSVC(6.0.3790.1830);
Thu, 21 Aug 2008 06:59:15 -0700
Received: from 10.7.240.237 ([10.7.240.237]) by namail5.corp.adobe.com
([10.8.192.88]) with Microsoft Exchange Server HTTP-DAV ;
Thu, 21 Aug 2008 13:59:15 +0000
User-Agent: Microsoft-Entourage/12.11.0.080522
Date: Thu, 21 Aug 2008 09:03:23 -0500
From: Henry Sinnreich <hsinnrei at adobe.com>
To: Dean Willis <dean.willis at softarmor.com>, Dan Wing <dwing at Cisco.COM>
Message-ID: <C4D2DFDB.7CB0%hsinnrei at adobe.com>
Thread-Topic: [Sip] Some comments on draft-ietf-sip-dtls-srtp-framework-02
Thread-Index: AckDlqxzZPPxehLrEU+b096swPHO/w==
In-Reply-To: <16BE241A-8699-485A-A450-BD27AA2EFAE6 at softarmor.com>
Mime-version: 1.0
X-OriginalArrivalTime: 21 Aug 2008 13:59:15.0884 (UTC)
FILETIME=[19289EC0:01C90396]
Cc: sip at ietf.org, ekr at rtfm.com
Subject: Re: [Sip] Some comments on draft-ietf-sip-dtls-srtp-framework-02
X-BeenThere: sip at 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 at ietf.org?subject=unsubscribe>
List-Post: <mailto:sip at ietf.org>
List-Help: <mailto:sip-request at ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/sip>,
<mailto:sip-request at ietf.org?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: sip-bounces at ietf.org
Errors-To: sip-bounces at ietf.org
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 at 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 statour 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 at cs.columbia.edu for questions on current sip
> Use sipping at 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 at cs.columbia.edu for questions on current sip
Use sipping at ietf.org for new developments on the application of sip
ement 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 at cs.columbia.edu for questions on current sip
> Use sipping at 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 at cs.columbia.edu for questions on current sip
Use sipping at ietf.org for new developments on the application of sip