[secdir] SecDir review of draft-ietf-payload-rtp-howto-09

Alexey Melnikov <alexey.melnikov@isode.com> Mon, 25 November 2013 15:06 UTC

Return-Path: <alexey.melnikov@isode.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 13D461ADEDC for <secdir@ietfa.amsl.com>; Mon, 25 Nov 2013 07:06:02 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.602
X-Spam-Level:
X-Spam-Status: No, score=-0.602 tagged_above=-999 required=5 tests=[BAYES_05=-0.5, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RP_MATCHES_RCVD=-0.001, SPF_PASS=-0.001] 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 iqJc70xy4Kin for <secdir@ietfa.amsl.com>; Mon, 25 Nov 2013 07:06:00 -0800 (PST)
Received: from statler.isode.com (statler.isode.com [62.3.217.254]) by ietfa.amsl.com (Postfix) with ESMTP id E75AD1ADEBE for <secdir@ietf.org>; Mon, 25 Nov 2013 07:05:59 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; t=1385391959; d=isode.com; s=selector; i=@isode.com; bh=c1SzDHf39F+tC6lby61QgvhQCN6qZFJt2BIRYowHRr4=; h=From:Sender:Reply-To:Subject:Date:Message-ID:To:Cc:MIME-Version: In-Reply-To:References:Content-Type:Content-Transfer-Encoding: Content-ID:Content-Description; b=CzO9AHB8Cjx3UUM527DR5YSaqYoGgKoPRte/hfw6vn13RI8D3UpA/EOWIPO+2HiLeu32ZB evf5cSjwvPssuSveAFrnawz9zpoOXY69bApDJskfC0Ael05uRSPs7nlUFAlDPMaHGOvUum 2Plz3xeOXevttu0u0thhUZs65cX1WmA=;
Received: from [172.16.1.29] (richard.isode.com [62.3.217.249]) by statler.isode.com (submission channel) via TCP with ESMTPA id <UpNnVgBtPKGj@statler.isode.com>; Mon, 25 Nov 2013 15:05:59 +0000
Message-ID: <52936755.1020204@isode.com>
Date: Mon, 25 Nov 2013 15:05:57 +0000
From: Alexey Melnikov <alexey.melnikov@isode.com>
User-Agent: Mozilla/5.0 (Windows NT 6.1; rv:17.0) Gecko/20130801 Thunderbird/17.0.8
To: IETF Security Directorate <secdir@ietf.org>, draft-ietf-payload-rtp-howto.all@tools.ietf.org
MIME-Version: 1.0
Content-Type: text/plain; charset="ISO-8859-1"; format="flowed"
Content-Transfer-Encoding: 7bit
Subject: [secdir] SecDir review of draft-ietf-payload-rtp-howto-09
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: Mon, 25 Nov 2013 15:06:02 -0000

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 document contains information on how to best write an RTP
payload format specification.  It provides reading tips, design
practices, and practical tips on how to produce an RTP payload format
specification quickly and with good results.  A template is also
included with instructions.

The Security Considerations section of the document points out that 
while the document doesn't have direct security considerations, it 
contains suggestions about what security considerations should be 
thought about when writing a new RTP payload format. I found these 
suggestions (last two paragraphs of Section 3.2.2, Section 6.1 and 
Section 7.2) to be quite complete/good. So I think the document is ready 
for publication.