IETF Logo Mail Archive

Re: [rtcweb] Adopting draft-muthu-behave-consent-freshness?

Christer Holmberg <christer.holmberg@ericsson.com> Mon, 09 September 2013 12:22 UTC

Return-Path: <christer.holmberg@ericsson.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 54A2F21E81AA for <rtcweb@ietfa.amsl.com>; Mon, 9 Sep 2013 05:22:29 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.249
X-Spam-Level:
X-Spam-Status: No, score=-6.249 tagged_above=-999 required=5 tests=[AWL=0.000, BAYES_00=-2.599, HELO_EQ_SE=0.35, RCVD_IN_DNSWL_MED=-4]
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 18DYaXj9b1LC for <rtcweb@ietfa.amsl.com>; Mon, 9 Sep 2013 05:22:16 -0700 (PDT)
Received: from mailgw1.ericsson.se (mailgw1.ericsson.se [193.180.251.45]) by ietfa.amsl.com (Postfix) with ESMTP id 34DE021E81BC for <rtcweb@ietf.org>; Mon, 9 Sep 2013 05:20:20 -0700 (PDT)
X-AuditID: c1b4fb2d-b7f738e000003ee3-d9-522dbd0398af
Received: from ESESSHC020.ericsson.se (Unknown_Domain [153.88.253.124]) by mailgw1.ericsson.se (Symantec Mail Security) with SMTP id 82.D0.16099.30DBD225; Mon, 9 Sep 2013 14:20:19 +0200 (CEST)
Received: from ESESSMB209.ericsson.se ([169.254.9.146]) by ESESSHC020.ericsson.se ([153.88.183.78]) with mapi id 14.02.0328.009; Mon, 9 Sep 2013 14:20:17 +0200
From: Christer Holmberg <christer.holmberg@ericsson.com>
To: Magnus Westerlund <magnus.westerlund@ericsson.com>, "rtcweb@ietf.org" <rtcweb@ietf.org>
Thread-Topic: [rtcweb] Adopting draft-muthu-behave-consent-freshness?
Thread-Index: AQHOrTfpPPSJ2RpCQEK9doXqsrtdnpm9T/RA
Date: Mon, 09 Sep 2013 12:20:16 +0000
Message-ID: <7594FB04B1934943A5C02806D1A2204B1C49B5A1@ESESSMB209.ericsson.se>
References: <522D88A8.3010209@ericsson.com>
In-Reply-To: <522D88A8.3010209@ericsson.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [153.88.183.19]
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFtrGLMWRmVeSWpSXmKPExsUyM+JvjS7zXt0gg72d/BZr/7WzOzB6LFny kymAMYrLJiU1J7MstUjfLoEr4/iJqawFnwQqHmw6xNLA+I23i5GTQ0LARGJB32k2CFtM4sK9 9UA2F4eQwGFGiV/X3kI5ixklpu/vYe9i5OBgE7CQ6P6nDdIgIhAr8X72VVYQW1jAReLZ3MOM EHFXiSmrrzFD2EYSH3a+ZwKxWQRUJE62fQazeQV8JZYd2wzWKySgLXFrxiR2EJtTQEdiw4Qf YAcxAh30/dQasHpmAXGJW0/mM0EcKiCxZM95ZghbVOLl43+sELaiRPvTBkaIej2JG1OnsEHY 2hLLFr5mhtgrKHFy5hOWCYyis5CMnYWkZRaSlllIWhYwsqxiZM9NzMxJLzfcxAgM+4Nbfuvu YDx1TuQQozQHi5I47ya9M4FCAumJJanZqakFqUXxRaU5qcWHGJk4OKUaGKUrT17k2Dp9PsN2 0QdTnkfw2uTPfRa+dvYLOe8HWnNVGPtFXPKWPvVb7d7z5czv7H7ll6F34lauzn61zXR2CI9D S3PUjsibj03vahgZ6O6delbF9cDMlwtYH1XUsM4+8JkzPLP5lHrtgoWXz0x49jEneZr/ytxj 65Zz9L4Ksdiveu+Pa0vWpi9KLMUZiYZazEXFiQAttHmnSQIAAA==
Subject: Re: [rtcweb] Adopting draft-muthu-behave-consent-freshness?
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, 09 Sep 2013 12:22:29 -0000

Hi,

I don't object adoption, but a question for clarification.

The draft says:

   "While a WebRTC browser could verify whether the peer continues to
   send SRTCP reports before sending traffic to the peer, the usage of
   SRTCP together with Security Descriptions [RFC4568] requires exposing
   the media keys to the JavaScript and renders SRTCP unsuitable for
   consent freshness."

Now, as we have decided to not use SDES, I guess that can be removed.

But, based on that, I'd just like to verify whether there is still a need for the draft :)

Regards,

Christer



-----Original Message-----
From: rtcweb-bounces@ietf.org [mailto:rtcweb-bounces@ietf.org] On Behalf Of Magnus Westerlund
Sent: 9. syyskuuta 2013 11:37
To: rtcweb@ietf.org
Subject: [rtcweb] Adopting draft-muthu-behave-consent-freshness?

WG,

This is a call for WG adoption of STUN Usage for Consent Freshness (draft-muthu-behave-consent-freshness-04). This document defines a STUN usage for consent freshness. As this requires no protocol extensions we as intended users can define this usage in our WG. Such work also matches our charter. The draft-ietf-rtcweb-security-arch-07 is normatively dependent on this STUN usage.

Document:
https://datatracker.ietf.org/doc/draft-muthu-behave-consent-freshness/

WG, please indicate your support or issues with adopting this document as WG item with a proposed milestone:

Mar 2014 Send STUN Usage for Consent Freshness to IESG for publication as proposed standard.

Cheers

Magnus Westerlund

----------------------------------------------------------------------
Multimedia Technologies, Ericsson Research EAB/TVM
----------------------------------------------------------------------
Ericsson AB                | Phone  +46 10 7148287
Färögatan 6                | Mobile +46 73 0949079
SE-164 80 Stockholm, Sweden| mailto: magnus.westerlund@ericsson.com
----------------------------------------------------------------------

_______________________________________________
rtcweb mailing list
rtcweb@ietf.org
https://www.ietf.org/mailman/listinfo/rtcweb

v2.23.0 | Report a Bug | By Email