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

Iñaki Baz Castillo <ibc@aliax.net> Fri, 26 April 2013 13:19 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 65F6021F9934 for <rtcweb@ietfa.amsl.com>; Fri, 26 Apr 2013 06:19:25 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.677
X-Spam-Level:
X-Spam-Status: No, score=-1.677 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, HTML_MESSAGE=0.001, MIME_8BIT_HEADER=0.3, NO_RELAYS=-0.001]
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 ToIktiVux3Jf for <rtcweb@ietfa.amsl.com>; Fri, 26 Apr 2013 06:19:25 -0700 (PDT)
Received: from mail-qc0-x22e.google.com (mail-qc0-x22e.google.com [IPv6:2607:f8b0:400d:c01::22e]) by ietfa.amsl.com (Postfix) with ESMTP id C02B321F992E for <rtcweb@ietf.org>; Fri, 26 Apr 2013 06:19:24 -0700 (PDT)
Received: by mail-qc0-f174.google.com with SMTP id z24so2074274qcq.19 for <rtcweb@ietf.org>; Fri, 26 Apr 2013 06:19:24 -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=I3Vx2ddVHUrLlyFryLef59T2vM/fP400IWMUnsJ49a4=; b=CSG34fxvVO9KOB/8BMeI9JTuuIHeIQN7OQubX7GmbLvOXU8E1r8ER7ynQ+2YBJ8V81 ROU0VmJ3Ukzdmaa+cSo5x97BzjGbA1UwQAUNnEvTQMNpTsfShVlNroXBIqd8ykKVFEYH wW2WZ5VDeuw9HDai0BKyYL9omZUYIJ8yY1bLHuemLU4k6CSseP2sfu8SxyGwjhd9COSi 8NXa43r+DBa/pVEL2UXgf3RTeDSZ9IfOI6g4E9nio1yvau0/9PYaUGApbJcZD5DQSsap 0xK0ZpjYM53m3k0EcLYjeuwCxCJnL/axN+abqLmd8OftzL3wCTrCeqN5aTBAU9XoVZlT 0mbQ==
MIME-Version: 1.0
X-Received: by 10.224.184.204 with SMTP id cl12mr40487521qab.0.1366982364234; Fri, 26 Apr 2013 06:19:24 -0700 (PDT)
Received: by 10.49.81.175 with HTTP; Fri, 26 Apr 2013 06:19:23 -0700 (PDT)
Received: by 10.49.81.175 with HTTP; Fri, 26 Apr 2013 06:19:23 -0700 (PDT)
In-Reply-To: <95219856-8365-4A7E-BD0B-4EECE8868498@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>
Date: Fri, 26 Apr 2013 15:19:23 +0200
Message-ID: <CALiegfkPtAhEq3yJqZ73sUYfkV1etKt53DE8C0jjYDu0HV1LYw@mail.gmail.com>
From: Iñaki Baz Castillo <ibc@aliax.net>
To: Tim Panton <tim@phonefromhere.com>
Content-Type: multipart/alternative; boundary="20cf302ef9d83c19ac04db4362f0"
X-Gm-Message-State: ALoCoQkTGAg0WGml6fCAwch2g4j1eRS8GlumpNBXSXCLt6exzTFq62D6gB7MyJC+dv/HCei2iiGr
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: Fri, 26 Apr 2013 13:19:25 -0000

The problem is when EKT is also used and the gateway must send SIP reINVITE
by itself as the proposed "solution diagram" shows. That is not just a
media gateway.

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

>
> On 26 Apr 2013, at 12:37, Iñaki Baz Castillo wrote:
>
> Such a solution requires a very expensive gateway. Good for vendors but
> bad for all the rest.
>
>
> I don't understand why the DTLS gateway would be so expensive. It is
> _exactly_ the same
> (conceptually) as the ICE processing - you filter off a few UDP packets
> from the stream, do some
> stuff, send replies then once you are happy you punt some dynamic settings
> back up to the (s)rtp
> layer.
>
> T.
>
>