IETF Logo Mail Archive

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

Iñaki Baz Castillo <ibc@aliax.net> Tue, 30 April 2013 14:52 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 2506721F9AD8 for <rtcweb@ietfa.amsl.com>; Tue, 30 Apr 2013 07:52:11 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.227
X-Spam-Level:
X-Spam-Status: No, score=-2.227 tagged_above=-999 required=5 tests=[AWL=0.450, 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 I4NpBODNAENw for <rtcweb@ietfa.amsl.com>; Tue, 30 Apr 2013 07:52:05 -0700 (PDT)
Received: from mail-qe0-f51.google.com (mail-qe0-f51.google.com [209.85.128.51]) by ietfa.amsl.com (Postfix) with ESMTP id DCA6321F9AB9 for <rtcweb@ietf.org>; Tue, 30 Apr 2013 07:52:04 -0700 (PDT)
Received: by mail-qe0-f51.google.com with SMTP id cz11so335322qeb.10 for <rtcweb@ietf.org>; Tue, 30 Apr 2013 07:52:04 -0700 (PDT)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=x-received:mime-version:in-reply-to:references:from:date:message-id :subject:to:cc:content-type:content-transfer-encoding :x-gm-message-state; bh=ToYCLlkqgnzv3OdYmPV6mH1AGbAiMxErWihHwiiz5Jc=; b=Gmuv2fjGqaNjXjWuv6mug3iWPi1pAMfs932iiuO1Hkoof9FL6gZifc6tzKeRWSIoZ4 7nCAjQRaLPqcNc2PpiiV7wGT5+zkrnIz+GHH7g6Jiaa8AsIk4pSC/KjZb+qW7CyUPPDH sPYmuFcHADSfu3nqZoTf0SwD5awoTAKc8v8CzOcVL4Gy/iEm1BjpZ+cGXPR3PywwFiDu G0C8jZmvrxnA8M/OY3WOH+i56ojL5jAj2lfPIsYSJWuhwdrtfNvxVLaX3I0FET18FdkI OKCDj1STIn6O6XmQXDyu3lSmCcoEXmw+eS+lm9XdwCjWECfst29A2p4svg503bcQQCOs a3cg==
X-Received: by 10.224.66.136 with SMTP id n8mr19128170qai.84.1367333524165; Tue, 30 Apr 2013 07:52:04 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.49.81.175 with HTTP; Tue, 30 Apr 2013 07:51:43 -0700 (PDT)
In-Reply-To: <5F38A528-70D7-414D-8462-BE3591EA26C1@cisco.com>
References: <3FA2E46D-C98E-4FC0-9F1D-AD595A861CE1@iii.ca> <517E0322.2060303@oracle.com> <53B9C161-C492-4F07-A9BD-75E17AE79AC9@phonefromhere.com> <CALiegfmg2365P7rKshdH4vrvh685WSXg6WTK6h+pkg=HRHS8_A@mail.gmail.com> <5F38A528-70D7-414D-8462-BE3591EA26C1@cisco.com>
From: Iñaki Baz Castillo <ibc@aliax.net>
Date: Tue, 30 Apr 2013 16:51:43 +0200
Message-ID: <CALiegfmTxLgBBpj9Uo-nQ4Qk4Nxjw8r2it9O0jtf2i_B0tUtKg@mail.gmail.com>
To: Dan Wing <dwing@cisco.com>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Gm-Message-State: ALoCoQlusypYY1OJ2E5c8XUheIWDiPntTNr4IssJOjVH2Gxi8ampUg1eC501JU6B1mxgduGIZnF2
Cc: "rtcweb@ietf.org" <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: Tue, 30 Apr 2013 14:52:14 -0000

2013/4/30 Dan Wing <dwing@cisco.com>:
>> - DTLS-EKT-SRTP:  This requires a gateway sending like "re-INVITE" for
>> common operations as multimedia session transfer, which involves the
>> gateway becoming both a media gateway and a complex signaling B2BUA
>> (and we hate that, right?).
>
> That re-INVITE is necessary because Security Descriptions changed the SRTP key, and Security Descriptions needs to send that re-INVITE.  It is not the fault of DTLS-SRTP-EKT, because it doesn't send a re-INVITE when the SRTP key changes (EKT handles key changes).
>
> If the objection is the re-INVITE when SRTP keys change, the solution is eliminating Security Descriptions.


The "solution" cannot be a media gateway that also must behave as a
complex signaling B2BUA originating re-INVITEs by itself, since that
means that a simple signaling pure proxy scenario is unfeasible.




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

v2.23.0 | Report a Bug | By Email