[rtcweb] #30: Wiretapping

"rtcweb issue tracker" <trac+rtcweb@trac.tools.ietf.org> Fri, 13 September 2013 00:08 UTC

MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: rtcweb issue tracker <trac+rtcweb@trac.tools.ietf.org>
Precedence: bulk
Auto-Submitted: auto-generated
To: draft-ietf-rtcweb-use-cases-and-requirements@tools.ietf.org, bernard_aboba@hotmail.com
Date: Fri, 13 Sep 2013 00:08:03 -0000
Message-ID: <066.e4120f60682a48aa7753e29f3071d4d8@trac.tools.ietf.org>
Resent-To: christer.holmberg@ericsson.com, goran.ap.eriksson@ericsson.com, stefan.lk.hakansson@ericsson.com
Resent-Message-Id: <20130913000807.19E4821E80ED@ietfa.amsl.com>
Resent-Date: Thu, 12 Sep 2013 17:08:05 -0700
Resent-From: trac+rtcweb@trac.tools.ietf.org
Cc: rtcweb@ietf.org
Subject: [rtcweb] #30: Wiretapping

#30: Wiretapping

 In several sections of the document, the phrase "It is essential
 that the communication cannot be wiretapped [RFC2804]" is used.
 The phrase is used in Sections 3.2.1.1, 3.2.11.1, 3.2.12.1, 3.2.13.1,
 3.3.1.1 and 3.2.3.1, but not in 3.2.14.1 (which also does not
 reference F20).

 Given the recent revelations, and the discussion of SRTP/SDES at
 IETF 87, I would suggest the following:

 a. Use of more precise terminology than what is in F20.  For example,
 I think what we are asking for in many of the F20 scenarios is
 per-packet encryption and integrity protection of media,
 utilizing keys known only by the endpoints, as well as support
 for perfect forward secrecy.

 b. Inclusion of a reference to F20 in Section 3.2.14.1 (Distributed
 Music Band).  Not sure why protection against snooping wouldn't be
 relevant in this use case (there are countries where musicians
 have been severely punished).

 c. Consideration of the requirement in gateway scenarios. For gateway
 scenarios such as 3.3.1.1, the e2e key management
 requirement probably isn't realistic, so maybe we need to
 just cite F35/F36 for that case.

-- 
-------------------------------------+-------------------------------------
 Reporter:                           |      Owner:  draft-ietf-rtcweb-use-
  bernard_aboba@hotmail.com          |  cases-and-
     Type:  defect                   |  requirements@tools.ietf.org
 Priority:  critical                 |     Status:  new
Component:  rtp-usage                |  Milestone:  milestone1
 Severity:  In WG Last Call          |    Version:  1.0
                                     |   Keywords:
-------------------------------------+-------------------------------------

Ticket URL: <http://tools.ietf.org/wg/rtcweb/trac/ticket/30>
rtcweb <http://tools.ietf.org/rtcweb/>

Re: [rtcweb] #30: Wiretapping Harald Alvestrand
[rtcweb] #30: Wiretapping rtcweb issue tracker
Re: [rtcweb] #30: Wiretapping rtcweb issue tracker
Re: [rtcweb] #30: Wiretapping rtcweb issue tracker