IETF Logo Mail Archive

Re: [rtcweb] SDP Security Descriptions (RFC 4568) and RTCWeb

Iñaki Baz Castillo <ibc@aliax.net> Sun, 28 April 2013 12:14 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 4A5C221F988A for <rtcweb@ietfa.amsl.com>; Sun, 28 Apr 2013 05:14:44 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.251
X-Spam-Level:
X-Spam-Status: No, score=-2.251 tagged_above=-999 required=5 tests=[AWL=-0.175, BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, HTML_MESSAGE=0.001, J_CHICKENPOX_43=0.6, 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 JUbENiFWZPZ9 for <rtcweb@ietfa.amsl.com>; Sun, 28 Apr 2013 05:14:43 -0700 (PDT)
Received: from mail-qe0-f43.google.com (mail-qe0-f43.google.com [209.85.128.43]) by ietfa.amsl.com (Postfix) with ESMTP id 83F1A21F97C4 for <rtcweb@ietf.org>; Sun, 28 Apr 2013 05:14:41 -0700 (PDT)
Received: by mail-qe0-f43.google.com with SMTP id f6so3585882qej.30 for <rtcweb@ietf.org>; Sun, 28 Apr 2013 05:14:41 -0700 (PDT)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=mime-version:x-received:in-reply-to:references:date:message-id :subject:from:to:cc:content-type:x-gm-message-state; bh=TfgdeAkLmDZn0BDprVtzPMDScu3B7U/4VB4x/epjmGE=; b=Pau1tmNZKFgGmWZ/Pxzxirt0SBBbgnbQpMzpH2f65lFsvfEfyszkKeTt+NS1/oFYSU X5Gbqf/4jv7r1vJVN+q1qu1nGuRUOH9FaHIVldInh7PiU6hnAOxS3aIY9sBlHB8CnDJb vTuCfr+pyhKROBgQPbB1obymWXiuvBJ0pzmHv9CdnHMrVlsBB+u4Oz2lVzTqx6XiNz+i 4XXH6P5uq/qHpAzzE+QrtIrTXQMRM4b4xVEodsbPTJcvSawVapu6Ta6orhf1f2NOmPcc BQoMWtbttUrYLWvfqNxXkeSiMwnBchthi5nwX6ujU990WMXEAQpFFXd15f4akk1oRrNa j5Fw==
MIME-Version: 1.0
X-Received: by 10.224.184.204 with SMTP id cl12mr47948465qab.0.1367151280902; Sun, 28 Apr 2013 05:14:40 -0700 (PDT)
Received: by 10.49.81.175 with HTTP; Sun, 28 Apr 2013 05:14:40 -0700 (PDT)
Received: by 10.49.81.175 with HTTP; Sun, 28 Apr 2013 05:14:40 -0700 (PDT)
In-Reply-To: <5A349C85-43C5-4DBE-BBD3-A42D59F8D297@phonefromhere.com>
References: <3FA2E46D-C98E-4FC0-9F1D-AD595A861CE1@iii.ca> <74300615-2293-4DCE-82A7-475F1A5A8256@gmail.com> <91B4F744-2201-4361-A8D8-7D36F47B865C@cisco.com> <CALiegfnqW26gEMYNpjJyzu=Nd6z9wCjvZbuY1N2tYvbfQiHyPA@mail.gmail.com> <95219856-8365-4A7E-BD0B-4EECE8868498@phonefromhere.com> <CALiegfkPtAhEq3yJqZ73sUYfkV1etKt53DE8C0jjYDu0HV1LYw@mail.gmail.com> <7594FB04B1934943A5C02806D1A2204B1C363631@ESESSMB209.ericsson.se> <5A349C85-43C5-4DBE-BBD3-A42D59F8D297@phonefromhere.com>
Date: Sun, 28 Apr 2013 14:14:40 +0200
Message-ID: <CALiegfnrLZM7FGD-b9dg5xeB9CBz_ia=3kF99wrxpG80YH3NnA@mail.gmail.com>
From: Iñaki Baz Castillo <ibc@aliax.net>
To: Tim Panton <tim@phonefromhere.com>
Content-Type: multipart/alternative; boundary="20cf302ef9d874008e04db6ab650"
X-Gm-Message-State: ALoCoQmXcosrD8H3LsIqeQZPHGn/9qu69zYkOYMa5MaZv7ltAart4OYZe2Uq53XyP8Jy4RRDfK8J
Cc: rtcweb@ietf.org
Subject: Re: [rtcweb] SDP Security Descriptions (RFC 4568) and RTCWeb
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: Sun, 28 Apr 2013 12:14:44 -0000

The problem is not DTLS (which can be handled by a pure media gateway) but
DTLS+EKT which means that the server should generate a reINVITE for legacy
interop (so the gateway would become a complex media+signaling B2BUA).

--
Iñaki Baz Castillo
<ibc@aliax.net>
El 28/04/2013 14:07, "Tim Panton" <tim@phonefromhere.com> escribió:

>
> On 27 Apr 2013, at 15:17, Christer Holmberg wrote:
>
>
> Hi,
>
> As I've mentioned before, we should really try to avoid solutions that
> require intermediaries to send reINVITEs - or, more general, send SDP
> offers.
>
> Regards,
>
> Christer
>
>
> If you stick to that rule, you'd want rid of ICE, SRTP, BUNDLE and all the
> other things an intermediary may have to add
> to a plain legacy device's offer in order for it to be acceptable to a
> browser.
>
> Or in other words: Why is the DTLS re-write especially irksome . ?
>
> T.
>
>
>
>
>

v2.23.0 | Report a Bug | By Email