IETF Logo Mail Archive

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

Iñaki Baz Castillo <ibc@aliax.net> Mon, 19 March 2012 12:25 UTC

Return-Path: <ibc@aliax.net>
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 8A09321F8656 for <rtcweb@ietfa.amsl.com>; Mon, 19 Mar 2012 05:25:14 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.619
X-Spam-Level:
X-Spam-Status: No, score=-2.619 tagged_above=-999 required=5 tests=[AWL=0.058, BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, MIME_8BIT_HEADER=0.3, RCVD_IN_DNSWL_LOW=-1]
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 qi3Ruatnoesv for <rtcweb@ietfa.amsl.com>; Mon, 19 Mar 2012 05:25:14 -0700 (PDT)
Received: from mail-vx0-f172.google.com (mail-vx0-f172.google.com [209.85.220.172]) by ietfa.amsl.com (Postfix) with ESMTP id E31F221F8643 for <rtcweb@ietf.org>; Mon, 19 Mar 2012 05:25:13 -0700 (PDT)
Received: by vcbfk13 with SMTP id fk13so7543042vcb.31 for <rtcweb@ietf.org>; Mon, 19 Mar 2012 05:25:13 -0700 (PDT)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc:content-type:content-transfer-encoding:x-gm-message-state; bh=VYeBLBRWuImqpgrKiTDEyAaCnmvrcmNZCjMKQXN2bak=; b=pxzCoqJLrH9ckQT54XG3B/Cny78i+ZZwO/Nka1+oH8vILp7aZIbUD5Ru6OxEti2SPX x29FHMw2ZeEZxl00MOjCgReOz3N14nGzIf6+AChiPvgnvOAsoAxprMxzEHFuxyy5Oexl EZ9kU/45VQ9ux8O7nJd815030KqgJe7MOwexoxiStVFg0O9AMixQHOAURfHuzA1N/vue z71lUvp776+vj98hyb7E674mzaFcDau1c4/mq8i9GF9766lBukAoUkMCe74cHLHxOgH4 TrA3ZBDA+VC1dkFmTxn/TBSYZEmtdys0WYmvYDNHAnvGN0JXovQC/cezWeM9cbfNLRr5 GqOw==
Received: by 10.52.90.111 with SMTP id bv15mr5667568vdb.34.1332159913406; Mon, 19 Mar 2012 05:25:13 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.52.170.165 with HTTP; Mon, 19 Mar 2012 05:24:53 -0700 (PDT)
In-Reply-To: <BLU169-W29E5B86F9E2C6F3126961C93420@phx.gbl>
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>
From: Iñaki Baz Castillo <ibc@aliax.net>
Date: Mon, 19 Mar 2012 13:24:53 +0100
Message-ID: <CALiegfk2aT+6Psr4nT-hG1G7eYRBfFCcT+25On2O4HfUXJ6-ng@mail.gmail.com>
To: Bernard Aboba <bernard_aboba@hotmail.com>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Gm-Message-State: ALoCoQlTVoqGcqyZnV9tUqPz6rolsep0ohTg9jAJRP56oWtVHqvsr5mdyniRhDBvNcVts3Wl13uH
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: Mon, 19 Mar 2012 12:25:14 -0000

2012/3/19 Bernard Aboba <bernard_aboba@hotmail.com>:
> At this point, support for SRTP is an expected feature on legacy equipment.
> For example, all the leading PSTN gateway vendors support SRTP already.  By the time RTCWEB specs are final, SRTP support will be very prevalent.


And if they don't support SRTP then bad luck for them. WebRTC cannot
be less secure and worse just because some SIP legacy equipments don't
implement a specification from 2004 (RFC 3711 - SRTP) !!

Please, make WebRTC as secure as possible for common usages in the
open Internet, rather than decreasing the security just to get
interoperability with telcos non supporting SRTP.

-- 
Iñaki Baz Castillo
<ibc@aliax.net>

v2.23.0 | Report a Bug | By Email