[Sipbrandy] Genart last call review of draft-ietf-sipbrandy-rtpsec-07

Pete Resnick <resnick@episteme.net> Tue, 05 March 2019 05:52 UTC

Return-Path: <resnick@episteme.net>
X-Original-To: sipbrandy@ietf.org
Delivered-To: sipbrandy@ietfa.amsl.com
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 9019F130FAE; Mon, 4 Mar 2019 21:52:43 -0800 (PST)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: Pete Resnick <resnick@episteme.net>
To: <gen-art@ietf.org>
Cc: sipbrandy@ietf.org, draft-ietf-sipbrandy-rtpsec.all@ietf.org, ietf@ietf.org
X-Test-IDTracker: no
X-IETF-IDTracker: 6.92.1
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <155176516348.5289.575681791142846479@ietfa.amsl.com>
Date: Mon, 04 Mar 2019 21:52:43 -0800
Archived-At: <https://mailarchive.ietf.org/arch/msg/sipbrandy/25n72RfwvoK-NK4qD2bCORZZHII>
Subject: [Sipbrandy] Genart last call review of draft-ietf-sipbrandy-rtpsec-07
X-BeenThere: sipbrandy@ietf.org
X-Mailman-Version: 2.1.29
List-Id: SIPBRANDY working group discussion list <sipbrandy.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/sipbrandy>, <mailto:sipbrandy-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/sipbrandy/>
List-Post: <mailto:sipbrandy@ietf.org>
List-Help: <mailto:sipbrandy-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/sipbrandy>, <mailto:sipbrandy-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 05 Mar 2019 05:52:44 -0000

Reviewer: Pete Resnick
Review result: Ready with Issues

I am the assigned Gen-ART reviewer for this draft. The General Area
Review Team (Gen-ART) reviews all IETF documents being processed
by the IESG for the IETF Chair.  Please treat these comments just
like any other last call comments.

For more information, please see the FAQ at


Document: draft-ietf-sipbrandy-rtpsec-07
Reviewer: Pete Resnick
Review Date: 2019-03-04
IETF LC End Date: 2019-02-21
IESG Telechat date: 2019-03-07


No concerns about the content of the document; looks like reasonable security

I'm not clear on why it's BCP (which usually implies "one and done") instead of
proposed standard; this thing looks like it could evolve with implementation
experience in the future. By no means a showstopper, but worth considering.
(Note that it doesn't require a new Last Call if you decide to change the