IETF Logo Mail Archive

Re: [rtcweb] No Interim on SDES at this juncture

"Vijaya Mandava (vimandav)" <vimandav@cisco.com> Wed, 12 June 2013 16:21 UTC

Return-Path: <vimandav@cisco.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 CCEA321E804B for <rtcweb@ietfa.amsl.com>; Wed, 12 Jun 2013 09:21:05 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.599
X-Spam-Level:
X-Spam-Status: No, score=-10.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8]
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 U1cVN-Xq-T9H for <rtcweb@ietfa.amsl.com>; Wed, 12 Jun 2013 09:20:57 -0700 (PDT)
Received: from rcdn-iport-8.cisco.com (rcdn-iport-8.cisco.com [173.37.86.79]) by ietfa.amsl.com (Postfix) with ESMTP id 700BF11E80E2 for <rtcweb@ietf.org>; Wed, 12 Jun 2013 09:20:52 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=761; q=dns/txt; s=iport; t=1371054054; x=1372263654; h=from:to:cc:subject:date:message-id:in-reply-to: content-id:content-transfer-encoding:mime-version; bh=tz2NzbvtNS3DRD11LeCdKrxQDy5Qla5AYm4ojLXRIc0=; b=IsXsDwmGriBxp7t0EgQqSj4UCglwdEPnmWr2UZlDYLEoipopglIYUHkX GGXxOLwp6YnsXRU3UVQTgtXfhf4Guc1hjxA1crS4nygmmqByJYapBAw4T BcfP/Qqjjtw0sP7bP9Mpgg5SEsG4daVUKC7TKZ9tj3y1u1UIMs+wF9VQ3 w=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AoAFAI2euFGtJXG//2dsb2JhbABagwl5gi28GoEDFnSCJQEEOj8SAQgiFEIlAgQBDQUIE4dzug+PEjEHgn9hA6kCgw+CJw
X-IronPort-AV: E=Sophos;i="4.87,853,1363132800"; d="scan'208";a="221959192"
Received: from rcdn-core2-4.cisco.com ([173.37.113.191]) by rcdn-iport-8.cisco.com with ESMTP; 12 Jun 2013 16:20:52 +0000
Received: from xhc-rcd-x15.cisco.com (xhc-rcd-x15.cisco.com [173.37.183.89]) by rcdn-core2-4.cisco.com (8.14.5/8.14.5) with ESMTP id r5CGKpPK031981 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Wed, 12 Jun 2013 16:20:51 GMT
Received: from xmb-rcd-x13.cisco.com ([169.254.3.169]) by xhc-rcd-x15.cisco.com ([173.37.183.89]) with mapi id 14.02.0318.004; Wed, 12 Jun 2013 11:20:51 -0500
From: "Vijaya Mandava (vimandav)" <vimandav@cisco.com>
To: Hadriel Kaplan <hadriel.kaplan@oracle.com>, Cullen Jennings <fluffy@iii.ca>
Thread-Topic: [rtcweb] No Interim on SDES at this juncture
Thread-Index: AQHOZrwis4fqLyH0zUuWk63gzW6WRpkxroOAgABdJQCAAHhHgP//0PcA
Date: Wed, 12 Jun 2013 16:20:51 +0000
Message-ID: <1CDFD781608D924094E43F573C351961B90AEC@xmb-rcd-x13.cisco.com>
In-Reply-To: <E42FA850-AF5F-4785-A3E6-5686451F9062@oracle.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [64.102.93.117]
Content-Type: text/plain; charset="us-ascii"
Content-ID: <1E87175110ADDB4091B15E11213CA917@emea.cisco.com>
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: "rtcweb@ietf.org" <rtcweb@ietf.org>
Subject: Re: [rtcweb] No Interim on SDES at this juncture
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: Wed, 12 Jun 2013 16:21:10 -0000

I absolutely agree. we need to find a solution to the incompatible SRTP
key exchange.

Thanks,
Vijaya

On 6/12/13 11:09 AM, "Hadriel Kaplan" <hadriel.kaplan@oracle.com> wrote:

>Instead we spent the time talking about IdP, which is a possible future
>need, rather than a current actual interoperability issue - which is what
>SRTP key exchange actually is.  At the last Sipit, one of the only
>interop issues found was incompatible SRTP key exchange.
>
>Hopefully there will be some standards-developing organization (SDO) out
>there that is responsible for media-plane interoperability of WebRTC
>hosts that can tackle the problem.  So far I've only found two SDOs that
>both seem to focus on browser APIs and what goes in HTTP.
>
>-hadriel

v2.23.0 | Report a Bug | By Email