Re: [secdir] Review of draft-ietf-xrblock-rtcp-xr-jb-12

Gonzalo Camarillo <Gonzalo.Camarillo@ericsson.com> Thu, 27 June 2013 15:05 UTC

Return-Path: <gonzalo.camarillo@ericsson.com>
X-Original-To: secdir@ietfa.amsl.com
Delivered-To: secdir@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 1227621F9E14; Thu, 27 Jun 2013 08:05:42 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -104.425
X-Spam-Level:
X-Spam-Status: No, score=-104.425 tagged_above=-999 required=5 tests=[AWL=1.824, BAYES_00=-2.599, HELO_EQ_SE=0.35, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
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 ArforAAVDDYJ; Thu, 27 Jun 2013 08:05:36 -0700 (PDT)
Received: from mailgw2.ericsson.se (mailgw2.ericsson.se [193.180.251.37]) by ietfa.amsl.com (Postfix) with ESMTP id 8BBE321F9E07; Thu, 27 Jun 2013 08:05:35 -0700 (PDT)
X-AuditID: c1b4fb25-b7f1e6d00000274b-39-51cc54be4874
Received: from esessmw0184.eemea.ericsson.se (Unknown_Domain [153.88.253.125]) by mailgw2.ericsson.se (Symantec Mail Security) with SMTP id F6.A8.10059.EB45CC15; Thu, 27 Jun 2013 17:05:34 +0200 (CEST)
Received: from [131.160.126.127] (153.88.115.8) by esessmw0184.eemea.ericsson.se (153.88.115.82) with Microsoft SMTP Server id 8.3.279.1; Thu, 27 Jun 2013 17:05:31 +0200
Message-ID: <51CC54B0.3050702@ericsson.com>
Date: Thu, 27 Jun 2013 18:05:20 +0300
From: Gonzalo Camarillo <Gonzalo.Camarillo@ericsson.com>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:17.0) Gecko/20130620 Thunderbird/17.0.7
MIME-Version: 1.0
To: Qin Wu <bill.wu@huawei.com>
References: <519097A8.40409@oracle.com> <51CAA254.6040303@oracle.com> <B8F9A780D330094D99AF023C5877DABA43B43D83@nkgeml501-mbs.china.huawei.com>
In-Reply-To: <B8F9A780D330094D99AF023C5877DABA43B43D83@nkgeml501-mbs.china.huawei.com>
X-Enigmail-Version: 1.5.1
Content-Type: text/plain; charset="ISO-8859-1"
Content-Transfer-Encoding: 7bit
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFlrFLMWRmVeSWpSXmKPExsUyM+Jvre6+kDOBBrMWGlg8nruA1WLeom3s FjP+TGS2+LDwIYtF3+tD7A6sHi1H3rJ6LFnyk8nj49NbLB5fLn9mC2CJ4rJJSc3JLEst0rdL 4Mo4cKaVteAof8WTRzvYGhh38XQxcnBICJhItN7l7WLkBDLFJC7cW8/WxcjFISRwilGi9fVs VpCEkMBaRon//zVAbF4BbYljDcuYQGwWAVWJa+8mgNWwCVhIbLl1nwXEFhWIkmjtncoMUS8o cXLmE7C4iIC8RMPmu4wgC5gF7jFKHN+xEKxZWMBcYsfed6wQm/sZJeb/7gfbwCkQJjHrUC8b xHmSEltetLOD2MwCehJTrrYwQtjyEtvfzmGGuFRbYvmzFpYJjEKzkCyfhaRlFpKWBYzMqxjZ cxMzc9LLjTYxAsP74JbfqjsY75wTOcQozcGiJM67We9MoJBAemJJanZqakFqUXxRaU5q8SFG Jg5OqQbGLpvHXVpXmncvL1ry1uZ2T6ld5dbvvouuOfTlcujNnjS1xCtyafa5pGju28Z9d4RW XdJR51kQ8vvi+z8T2t7cz1QWeKr8Ld3635R1wacE132//l/pWrOhX/Oa/pLPbMusvR5Zfvm7 /J38O//3/D3Po79ILH+v73r9N6PB42ZPx77mLxraC4r0lViKMxINtZiLihMB8zZusD0CAAA=
Cc: "draft-ietf-xrblock-rtcp-xr-jb.all@tools.ietf.org" <draft-ietf-xrblock-rtcp-xr-jb.all@tools.ietf.org>, "iesg@ietf.org" <iesg@ietf.org>, "secdir@ietf.org" <secdir@ietf.org>
Subject: Re: [secdir] Review of draft-ietf-xrblock-rtcp-xr-jb-12
X-BeenThere: secdir@ietf.org
X-Mailman-Version: 2.1.12
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: Thu, 27 Jun 2013 15:05:42 -0000

Hi,

note that RTP is one of the well-known abbreviations that do not need
expansion:

http://www.rfc-editor.org/rfc-style-guide/abbrev.expansion.txt

Cheers,

Gonzalo

On 26/06/2013 12:46 PM, Qin Wu wrote:
> Hi,Shawn:
> Thank for your comments, my reply is inline below.
> 
> Regards!
> -Qin
> 
> -----Original Message-----
> From: Shawn M Emery [mailto:shawn.emery@oracle.com] 
> Sent: Wednesday, June 26, 2013 4:12 PM
> To: secdir@ietf.org
> Cc: draft-ietf-xrblock-rtcp-xr-jb.all@tools.ietf.org; iesg@ietf.org
> Subject: Review of draft-ietf-xrblock-rtcp-xr-jb-12
> 
> 
> 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.
> 
> This internet-draft specifies a RTP Control Protocol (RTCP) Extended Report
> (XR) Block for data on jitter buffer configuration and performance.
> 
> The security considerations section does exist and states that the new block
> data does not introduce any additional security concerns than those stated
> in the base XR spec, RFC 3611.  I believe this to be an accurate assertion.
> 
> General comments:
> 
> I found the draft slightly hard to read, as the terminology and abbreviations
> used are not expanded.  For example, the abstract has "RTP", but never expands
> the abbreviation.
> 
> [Qin]; RTP is abbreviation of  "A Transport Protocol for Real-Time Applications" and defined
> In the basic RTP protocol specification [RFC3550], it is the basic atom we are used 
> in the context of this draft and can not be decomposed.For other term and abbreviation,
> I will check and fix that, thanks.
> 
> 
> Editorial comments:
> 
> s/[RFC6390]and/[RFC6390] and/
> 
> [Qin]:okay.Thanks!
> 
> Shawn.
> --
> 
>