IETF Logo Mail Archive

Re: [rtcweb] Use Case draft - Eavesdropping.

"Hutton, Andrew" <andrew.hutton@siemens-enterprise.com> Tue, 01 May 2012 13:14 UTC

Return-Path: <andrew.hutton@siemens-enterprise.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 A383721E80C8 for <rtcweb@ietfa.amsl.com>; Tue, 1 May 2012 06:14:22 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.561
X-Spam-Level:
X-Spam-Status: No, score=-2.561 tagged_above=-999 required=5 tests=[AWL=0.038, BAYES_00=-2.599]
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 5CyzuUryrlgx for <rtcweb@ietfa.amsl.com>; Tue, 1 May 2012 06:14:21 -0700 (PDT)
Received: from senmx12-mx.siemens-enterprise.com (senmx12-mx.siemens-enterprise.com [62.134.46.10]) by ietfa.amsl.com (Postfix) with ESMTP id 93D4C21E8053 for <rtcweb@ietf.org>; Tue, 1 May 2012 06:14:21 -0700 (PDT)
Received: from MCHP064A.global-ad.net (unknown [172.29.37.63]) by senmx12-mx.siemens-enterprise.com (Server) with ESMTP id 4B57323F04A8; Tue, 1 May 2012 15:14:20 +0200 (CEST)
Received: from MCHP058A.global-ad.net ([172.29.37.55]) by MCHP064A.global-ad.net ([172.29.37.63]) with mapi; Tue, 1 May 2012 15:14:20 +0200
From: "Hutton, Andrew" <andrew.hutton@siemens-enterprise.com>
To: Ted Hardie <ted.ietf@gmail.com>, "rtcweb@ietf.org" <rtcweb@ietf.org>
Date: Tue, 01 May 2012 15:14:18 +0200
Thread-Topic: [rtcweb] Use Case draft - Eavesdropping.
Thread-Index: Ac0kkPiuwYinP6GjTFWYkg4o1GLBJQDCjZYg
Message-ID: <101C6067BEC68246B0C3F6843BCCC1E312992828BD@MCHP058A.global-ad.net>
References: <CA+9kkMCYArLPRP3c00UdOja64WRT6ghN0PSy7XvM_wbxBBB+vA@mail.gmail.com>
In-Reply-To: <CA+9kkMCYArLPRP3c00UdOja64WRT6ghN0PSy7XvM_wbxBBB+vA@mail.gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
acceptlanguage: en-US
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Subject: Re: [rtcweb] Use Case draft - Eavesdropping.
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, 01 May 2012 13:14:22 -0000

Hi,

A number of use cases within Draft-ietf-rtcweb-use-cases-and-requirements-07 contain the statement "It is essential that the communication cannot be eavesdropped" however there is no definition of what is actually meant by "eavesdropped" although I think we all have an idea of what it means.

Maybe it would be better to replace these statements with something that refers to wiretapping and RFC 2804 (RAVEN) which actually has a definition of wiretapping.

Regards
Andy




> -----Original Message-----
> From: rtcweb-bounces@ietf.org [mailto:rtcweb-bounces@ietf.org] On
> Behalf Of Ted Hardie
> Sent: 27 April 2012 17:15
> To: rtcweb@ietf.org
> Subject: [rtcweb] Use Case draft
> 
> The chairs would like to ask the working group to focus on the use
> case draft.  If you have use cases that need to be added to the
> document or text changes you'd like to suggest, please send them in
> for discussion before May 15th.  After this round, we will look toward
> having a working group last call on the document (hopefully before the
> interim meeting).
> 
> regards,
> 
> Ted, Magnus, Cullen
> _______________________________________________
> rtcweb mailing list
> rtcweb@ietf.org
> https://www.ietf.org/mailman/listinfo/rtcweb

v2.23.0 | Report a Bug | By Email