[AVTCORE] Roman Danyliw's No Objection on draft-ietf-payload-tsvcis-03: (with COMMENT)
Roman Danyliw via Datatracker <noreply@ietf.org> Tue, 01 October 2019 14:03 UTC
Return-Path: <noreply@ietf.org>
X-Original-To: avt@ietf.org
Delivered-To: avt@ietfa.amsl.com
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 1C9EA12083D; Tue, 1 Oct 2019 07:03:26 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 8bit
From: Roman Danyliw via Datatracker <noreply@ietf.org>
To: The IESG <iesg@ietf.org>
Cc: draft-ietf-payload-tsvcis@ietf.org, Ali Begen <ali.begen@networked.media>, avtcore-chairs@ietf.org, ali.begen@networked.media, avt@ietf.org
X-Test-IDTracker: no
X-IETF-IDTracker: 6.103.1
Auto-Submitted: auto-generated
Precedence: bulk
Reply-To: Roman Danyliw <rdd@cert.org>
Message-ID: <156993860610.23632.14112555733358406719.idtracker@ietfa.amsl.com>
Date: Tue, 01 Oct 2019 07:03:26 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/avt/HAEvN5KhwGlKjs0m4FVDPV9wBDQ>
Subject: [AVTCORE] Roman Danyliw's No Objection on draft-ietf-payload-tsvcis-03: (with COMMENT)
X-BeenThere: avt@ietf.org
X-Mailman-Version: 2.1.29
List-Id: Audio/Video Transport Core Maintenance <avt.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/avt>, <mailto:avt-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/avt/>
List-Post: <mailto:avt@ietf.org>
List-Help: <mailto:avt-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/avt>, <mailto:avt-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 01 Oct 2019 14:03:36 -0000
Roman Danyliw has entered the following ballot position for draft-ietf-payload-tsvcis-03: No Objection When responding, please keep the subject line intact and reply to all email addresses included in the To and CC lines. (Feel free to cut this introductory paragraph, however.) Please refer to https://www.ietf.org/iesg/statement/discuss-criteria.html for more information about IESG DISCUSS and COMMENT positions. The document, along with other ballot positions, can be found here: https://datatracker.ietf.org/doc/draft-ietf-payload-tsvcis/ ---------------------------------------------------------------------- COMMENT: ---------------------------------------------------------------------- Section 2. Per “In most IP-based network deployments, standard link encryption methods (SRTP , VPNs, FIPS 140 link encryptors or Type 1 Ethernet encryptors) would be used to secure the RTP speech contents.”, the inclusion of STRP in this list of “link encryption” methods was surprising. The other methods typically provide a service agnostic tunnel but STRP is application specific (and doesn’t protect a link). Section 8, Per “Applications SHOULD use one or more appropriate strong security mechanisms”, what exactly is the “SHOULD” requiring?
- [AVTCORE] Roman Danyliw's No Objection on draft-i… Roman Danyliw via Datatracker
- Re: [AVTCORE] Roman Danyliw's No Objection on dra… Roni Even (A)