[secdir] Secdir last call review of draft-ietf-avtext-framemarking-13

Carl Wallace via Datatracker <noreply@ietf.org> Mon, 11 April 2022 10:32 UTC

Return-Path: <noreply@ietf.org>
X-Original-To: secdir@ietf.org
Delivered-To: secdir@ietfa.amsl.com
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 3CAE13A1328; Mon, 11 Apr 2022 03:32:25 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: Carl Wallace via Datatracker <noreply@ietf.org>
To: secdir@ietf.org
Cc: avt@ietf.org, draft-ietf-avtext-framemarking.all@ietf.org, last-call@ietf.org
X-Test-IDTracker: no
X-IETF-IDTracker: 7.46.0
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <164967314513.32128.2582071611829692564@ietfa.amsl.com>
Reply-To: Carl Wallace <carl@redhoundsoftware.com>
Date: Mon, 11 Apr 2022 03:32:25 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/secdir/NE9voCsSMXrKEOWQSP880venwAg>
Subject: [secdir] Secdir last call review of draft-ietf-avtext-framemarking-13
X-BeenThere: secdir@ietf.org
X-Mailman-Version: 2.1.29
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: Mon, 11 Apr 2022 10:32:26 -0000

Reviewer: Carl Wallace
Review result: Ready

This is an experimental document that describes a Frame Marking RTP header
extension used to convey information about video frames that is critical for
error recovery and packet forwarding in RTP middleboxes or network nodes. It is
well written and ready to go. The only minor comment I had was that the
security considerations may benefit from a reference to the security
considerations in RFC 8285, if only to pull in the SHOULD regarding header
integrity protection.