[secdir] SecDir review of draft-ietf-avtcore-rtp-topologies-update-08

Alexey Melnikov <alexey.melnikov@isode.com> Wed, 24 June 2015 15:42 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 []) by ietfa.amsl.com (Postfix) with ESMTP id D4C191ACCDF for <secdir@ietfa.amsl.com>; Wed, 24 Jun 2015 08:42:36 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.011
X-Spam-Status: No, score=-2.011 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01] autolearn=ham
Received: from mail.ietf.org ([]) by localhost (ietfa.amsl.com []) (amavisd-new, port 10024) with ESMTP id QSw8F_aPPoSu for <secdir@ietfa.amsl.com>; Wed, 24 Jun 2015 08:42:35 -0700 (PDT)
Received: from waldorf.isode.com (waldorf.isode.com []) by ietfa.amsl.com (Postfix) with ESMTP id B00131ACD00 for <secdir@ietf.org>; Wed, 24 Jun 2015 08:42:35 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; t=1435160555; d=isode.com; s=selector; i=@isode.com; bh=6/+7TZn+OYhyJd07ehdIAtnSoGyY9B5PkGat1/7fEqg=; 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=q3okRoZrT2Sz2P9CA7Ufu0AUq/StAsIrbfP6I37NBaX+Uv+Jk5jY3+B3rRd50OeiUPRVZi FfOI2hO8WxtXeG/7BkkJU362WUv0gHh91FAcwItZ9tT5ahOLbDOFlSQRzvHCNGA2CYK433 /c2+r34mugC7n4aKDJFtpR0xYBTqQcc=;
Received: from [] (dhcp-215.isode.net []) by waldorf.isode.com (submission channel) via TCP with ESMTPSA id <VYrP6gA3=0L7@waldorf.isode.com>; Wed, 24 Jun 2015 16:42:34 +0100
Message-ID: <558ACFDE.5000109@isode.com>
Date: Wed, 24 Jun 2015 16:42:22 +0100
From: Alexey Melnikov <alexey.melnikov@isode.com>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:31.0) Gecko/20100101 Thunderbird/31.7.0
To: IETF Security Directorate <secdir@ietf.org>, draft-ietf-avtcore-rtp-topologies-update.all@tools.ietf.org
MIME-Version: 1.0
Content-Type: text/plain; charset="windows-1252"; format="flowed"
Content-Transfer-Encoding: 7bit
Archived-At: <http://mailarchive.ietf.org/arch/msg/secdir/Qhfc4RvCWnAy0OBDX9KN6G7nJ2U>
Subject: [secdir] SecDir review of draft-ietf-avtcore-rtp-topologies-update-08
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: <https://mailarchive.ietf.org/arch/browse/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: Wed, 24 Jun 2015 15:42:37 -0000

(My apologies for doing the review late.)

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 discusses point to point and multi-endpoint topologies
used in Real-time Transport Protocol (RTP)-based environments.  In
particular, centralized topologies commonly employed in the video
conferencing industry are mapped to the RTP terminology.

This document is updated with additional topologies and replaces RFC


The document is well written and has lots of useful security related 
details. I have very passing familiarity with RTP/RTCP, but the Security 
Considerations looks reasonable to me.