IETF Logo Mail Archive

Re: [rtcweb] Resolving RTP/SDES question in Paris

Bernard Aboba <bernard_aboba@hotmail.com> Tue, 20 March 2012 11:03 UTC

Return-Path: <bernard_aboba@hotmail.com>
X-Original-To: rtcweb@ietfa.amsl.com
Delivered-To: rtcweb@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6046D21F865F for <rtcweb@ietfa.amsl.com>; Tue, 20 Mar 2012 04:03:19 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.129
X-Spam-Level:
X-Spam-Status: No, score=-102.129 tagged_above=-999 required=5 tests=[AWL=0.469, BAYES_00=-2.599, HTML_MESSAGE=0.001, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id V-Pb8UYSDs9e for <rtcweb@ietfa.amsl.com>; Tue, 20 Mar 2012 04:03:18 -0700 (PDT)
Received: from blu0-omc2-s30.blu0.hotmail.com (blu0-omc2-s30.blu0.hotmail.com [65.55.111.105]) by ietfa.amsl.com (Postfix) with ESMTP id BF5C221F8622 for <rtcweb@ietf.org>; Tue, 20 Mar 2012 04:03:18 -0700 (PDT)
Received: from BLU169-W14 ([65.55.111.71]) by blu0-omc2-s30.blu0.hotmail.com with Microsoft SMTPSVC(6.0.3790.4675); Tue, 20 Mar 2012 04:03:17 -0700
Message-ID: <BLU169-W14350ED73665078A033F7C93430@phx.gbl>
Content-Type: multipart/alternative; boundary="_190eeef6-b397-46e1-9cf2-2cdbb7645224_"
X-Originating-IP: [99.32.177.175]
From: Bernard Aboba <bernard_aboba@hotmail.com>
To: andrew.hutton@siemens-enterprise.com
Date: Tue, 20 Mar 2012 04:03:17 -0700
Importance: Normal
In-Reply-To: <101C6067BEC68246B0C3F6843BCCC1E31296AE222A@MCHP058A.global-ad.net>
References: <4F4759DC.7060303@ericsson.com><387F9047F55E8C42850AD6B3A7A03C6C0E1FEB69@inba-mail01.sonusnet.com><CALiegfnkYVEpmPV-zSL_4wOY-HiFZN-qJCQCiioaS=5NaqhLZw@mail.gmail.com><CAD5OKxvtOAxMBx6xDnyfTnEq76oDEm6uj1xL6wGjjrtKUAHy3g@mail.gmail.com><CABcZeBNZiotPmCfT53uEo+O0xw4xv6tXW1M_G-3A5BHuncsduA@mail.gmail.com><CAD5OKxvYOY5JZ2mYNGiH1poUBQkyOOycePFijH5H+SxtcdqujQ@mail.gmail.com><CABkgnnVe-b6Sv=R67bMJk_NQqQwdrRUn6rBm7Gu_CMcfPQwtEg@mail.gmail.com><CAD5OKxvZbEJ7sV4WPAYoQapzMR_QwAftj-oKg=ioMKHNT792wQ@mail.gmail.com><6F428EFD2B8C2F49A2FB1317291A76C113563C5A92@USNAVSXCHMBSA1.ndc.alcatel-lucent.com><CALiegf=jtkDCS_D0ZFe9UpbiadQ0vsJ+4MppQSbLr-wbaXNrfQ@mail.gmail.com><BLU169-W29E5B86F9E2C6F3126961C93420@phx.gbl><CALiegfk2aT+6Psr4nT-hG1G7eYRBfFCcT+25On2O4HfUXJ6-ng@mail.gmail.com><CAD6AjGSmi9j+sdGWPts20-iwGvGij05ek0OKYEPULC6B=aFpQg@mail.gmail.com><6F428EFD2B8C2F49A2FB1317291A76C113564482A7@USNAVSXCHMBSA1.ndc.alcatel-lucent.com><ADBB75F3-E20C-4EC4-B9C3-EF2E4BFF409C@phonefromhere.com><C!, AD5OKxvuE V8Vbq3h7=Zgc, KmREjmguvz5n-SpXr2n-EY7a_ddxg@mail.gmail.com><CALiegfk1ozOKPcDjbd3H_z2Edzh4RcZpYyJSWdw_1DJ04muQXA@mail.gmail.com><CAD5OKxu8-+0O0=eE7mD1hi=nPUpEXczGj=bRNQCQL1BW8c-c-Q@mail.gmail.com>, <D75A384B-0F38-4E30-8C03-12E903A69B64@acmepacket.com>, <E17CAD772E76C742B645BD4DC602CD8105EBE8CF@NAHALD.us.int.genesyslab.com>, <387F9047F55E8C42850AD6B3A7A03C6C0E1FFE23@inba-mail01.sonusnet.com>, <2E10EB15-7E2E-47B9-80D1-5244DDE5FDF7@acmepacket.com>, <101C6067BEC68246B0C3F6843BCCC1E31296AE222A@MCHP058A.global-ad.net>
MIME-Version: 1.0
X-OriginalArrivalTime: 20 Mar 2012 11:03:17.0919 (UTC) FILETIME=[0E0642F0:01CD0689]
Cc: rtcweb@ietf.org
Subject: Re: [rtcweb] Resolving RTP/SDES question in Paris
X-BeenThere: rtcweb@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Real-Time Communication in WEB-browsers working group list <rtcweb.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/rtcweb>, <mailto:rtcweb-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/rtcweb>
List-Post: <mailto:rtcweb@ietf.org>
List-Help: <mailto:rtcweb-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/rtcweb>, <mailto:rtcweb-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 20 Mar 2012 11:03:19 -0000

Any said: 

> The recording system should be able to work with DTLS-SRTP but it will most likely act as a MITM so will change the DTLS fingerprint. I don't see that as a problem.

[BA] One of the questions I have had about the usage of DTLS-SRTP contemplated in RTCWEB is whether it will be interoperable with the SIP usage of DTLS-SRTP.  

In the SIP framework it is possible to do RFC 4474 re-signing in the B2BUA if the destination is an E.164 number. 

However, the DTLS-SRTP/IdP framework seems to assume that the identities are email-style addresses.

v2.23.0 | Report a Bug | By Email