Re: [secdir] secdir review of draft-ietf-xrblock-rtcp-xr-post-repair-loss-count-07

"Huangyihong (Rachel)" <rachel.huang@huawei.com> Tue, 23 December 2014 00:45 UTC

Return-Path: <rachel.huang@huawei.com>
X-Original-To: secdir@ietfa.amsl.com
Delivered-To: secdir@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 352061A8934; Mon, 22 Dec 2014 16:45:01 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.211
X-Spam-Level:
X-Spam-Status: No, score=-4.211 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 80cqockGX1Pz; Mon, 22 Dec 2014 16:44:59 -0800 (PST)
Received: from lhrrgout.huawei.com (lhrrgout.huawei.com [194.213.3.17]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 753181A6FE8; Mon, 22 Dec 2014 16:44:58 -0800 (PST)
Received: from 172.18.7.190 (EHLO lhreml403-hub.china.huawei.com) ([172.18.7.190]) by lhrrg01-dlp.huawei.com (MOS 4.3.7-GA FastPath queued) with ESMTP id BQJ14189; Tue, 23 Dec 2014 00:44:57 +0000 (GMT)
Received: from nkgeml405-hub.china.huawei.com (10.98.56.36) by lhreml403-hub.china.huawei.com (10.201.5.217) with Microsoft SMTP Server (TLS) id 14.3.158.1; Tue, 23 Dec 2014 00:44:56 +0000
Received: from NKGEML501-MBS.china.huawei.com ([169.254.2.169]) by nkgeml405-hub.china.huawei.com ([10.98.56.36]) with mapi id 14.03.0158.001; Tue, 23 Dec 2014 08:44:51 +0800
From: "Huangyihong (Rachel)" <rachel.huang@huawei.com>
To: Scott Kelly <scott@hyperthought.com>, "secdir@ietf.org" <secdir@ietf.org>, "iesg@ietf.org" <iesg@ietf.org>, "draft-ietf-xrblock-rtcp-xr-post-repair-loss-count.all@tools.ietf.org" <draft-ietf-xrblock-rtcp-xr-post-repair-loss-count.all@tools.ietf.org>
Thread-Topic: secdir review of draft-ietf-xrblock-rtcp-xr-post-repair-loss-count-07
Thread-Index: AQHQHe67w71WGaG2g0awosmV7furIpycVtlA
Date: Tue, 23 Dec 2014 00:44:50 +0000
Message-ID: <51E6A56BD6A85142B9D172C87FC3ABBB862A172A@nkgeml501-mbs.china.huawei.com>
References: <EEB37667-C060-4610-A9DF-83192FA17E18@hyperthought.com>
In-Reply-To: <EEB37667-C060-4610-A9DF-83192FA17E18@hyperthought.com>
Accept-Language: zh-CN, en-US
Content-Language: zh-CN
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [10.138.41.144]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-CFilter-Loop: Reflected
Archived-At: http://mailarchive.ietf.org/arch/msg/secdir/elYMG4n1VYYtI1fZRhdbBiaXJds
X-Mailman-Approved-At: Fri, 26 Dec 2014 09:30:05 -0800
Subject: Re: [secdir] secdir review of draft-ietf-xrblock-rtcp-xr-post-repair-loss-count-07
X-BeenThere: secdir@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: Security Area Directorate <secdir.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/secdir>, <mailto:secdir-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/secdir/>
List-Post: <mailto:secdir@ietf.org>
List-Help: <mailto:secdir-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/secdir>, <mailto:secdir-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 23 Dec 2014 00:45:01 -0000

Hi Scott,

Thanks for your suggestions. I'll remove "It is believed that" from current draft.

BR,
Rachel

> -----Original Message-----
> From: Scott Kelly [mailto:scott@hyperthought.com]
> Sent: Monday, December 22, 2014 9:53 PM
> To: secdir@ietf.org; iesg@ietf.org;
> draft-ietf-xrblock-rtcp-xr-post-repair-loss-count.all@tools.ietf.org
> Subject: secdir review of draft-ietf-xrblock-rtcp-xr-post-repair-loss-count-07
> 
> I have reviewed this document as part of the security directorate's ongoing
> effort to review all IETF documents being processed by the IESG.  These
> comments were written primarily for the benefit of the security area directors.
> Document editors and WG chairs should treat these comments just like any
> other last call comments.
> 
> Here's the abstract:
> 
>    This document defines an RTP Control Protocol (RTCP) Extended Report
>    (XR) Block that allows reporting of post-repair loss count metrics
>    for a range of RTP applications.
> 
> Prior to this mechanism, RTCP Sender Reports (SR)/Receiver Reports (RR)
> contain, among other things, the cumulative number of packets lost. That
> number doesn't indicate the data successfully received, because the receiver
> can apply repair mechanisms to recover data. This document adds reporting for
> post-repair metrics.
> 
> The security considerations seem complete, but I have one nit. Here's the first
> sentence:
> 
>    It is believed that this RTCP XR block introduces no new security
>    considerations beyond those described in [RFC3611].
> 
> Who believes this? I would simply assert this (remove "It is believed that"),
> and if I wasn't comfortable with that, I'd take that as an indication that more
> analysis is required.
> 
> -Scott
> 
>