[AVTCORE] Éric Vyncke's Discuss on draft-ietf-avtcore-rtp-scip-08: (with DISCUSS and COMMENT)
Éric Vyncke via Datatracker <noreply@ietf.org> Fri, 02 February 2024 13:34 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 70070C14F5EF; Fri, 2 Feb 2024 05:34:12 -0800 (PST)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 8bit
From: Éric Vyncke via Datatracker <noreply@ietf.org>
To: The IESG <iesg@ietf.org>
Cc: draft-ietf-avtcore-rtp-scip@ietf.org, avtcore-chairs@ietf.org, avt@ietf.org, jonathan.lennox@8x8.com, bernard.aboba@gmail.com, bernard.aboba@gmail.com
X-Test-IDTracker: no
X-IETF-IDTracker: 12.4.0
Auto-Submitted: auto-generated
Precedence: bulk
Reply-To: Éric Vyncke <evyncke@cisco.com>
Message-ID: <170688085244.27140.3271707817213892752@ietfa.amsl.com>
Date: Fri, 02 Feb 2024 05:34:12 -0800
Archived-At: <https://mailarchive.ietf.org/arch/msg/avt/nQjGkmpOWPrH3YkrcZY0f_9dLOA>
Subject: [AVTCORE] Éric Vyncke's Discuss on draft-ietf-avtcore-rtp-scip-08: (with DISCUSS and COMMENT)
X-BeenThere: avt@ietf.org
X-Mailman-Version: 2.1.39
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: Fri, 02 Feb 2024 13:34:12 -0000
Éric Vyncke has entered the following ballot position for draft-ietf-avtcore-rtp-scip-08: Discuss 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/about/groups/iesg/statements/handling-ballot-positions/ for more information about how to handle DISCUSS and COMMENT positions. The document, along with other ballot positions, can be found here: https://datatracker.ietf.org/doc/draft-ietf-avtcore-rtp-scip/ ---------------------------------------------------------------------- DISCUSS: ---------------------------------------------------------------------- # Éric Vyncke, INT AD, comments for draft-ietf-avtcore-rtp-scip-05 Thank you for the work put into this document. Alas, even after some email discussions with the authors, the core of my discuss is still there. So, I cannot clear my discuss. Previous DISCUSS is at: https://mailarchive.ietf.org/arch/msg/avt/xFC3Ux9AfYt3e5T0GSzrasQe_j4/ # DISCUSS As noted in https://www.ietf.org/blog/handling-iesg-ballot-positions/, a DISCUSS ballot is a request to have a discussion on the following topics: ## Section 3 and abstract I am afraid that without free and public access to the IETF community (whether informational or normative) to the SCIP protocol itself, the IETF stream cannot publish any document (even informational or experimental) with the following assertions/claims: - `SCIP is an application layer protocol that provides ... security services such as confidentiality and integrity protection` - `The SCIP protocol defined in SCIP-210 [SCIP210] includes ... security services such as end-to-end confidentiality and integrity protection.` Indeed, all IETF stream documents require that the IETF community was able to review it. The nature of SCIP standard has prevented such review, therefore, it is not possible for an IETF stream document to make those claims (that are probably correct). Suggest removing any such claim from the text or rephrasing them so that they do not appear as an IETF claim, e.g., "NATO claims that..." or "NATO certifies that ..." ---------------------------------------------------------------------- COMMENT: ---------------------------------------------------------------------- # COMMENTS ## Abstract Is there a reason why is SDP expanded and not RTP ? ## Section 1 Unsure whether the following text has a place into an IETF RFC `This document provides a reference for network security policymakers, network equipment OEMs, procurement personnel, and government agency and commercial industry representatives.`. Suggest to remove it. I wonder to wonder whether the USA has left NATO ? The text `SCIP is presently implemented in United States and NATO` seems to indicate that the USA are not included in NATO. ## Section 1.2 The DTX acronym is expanded twice and never used. Suggest to remove it. ## Section 2 Per `Secure Communication Interoperability Protocol (SCIP) allows the negotiation of several voice, data, and video applications`, it appears that SCIP can also be used for *data*, but this document is only about video/audio. I.e., some text should explain to the reader what happens to the data. Please explain what is a STANAG or provide an informational reference to STANAG 5068. The reader will welcome explanations about the numbers in `scip/8000 and scip/90000` (e.g., by a reference to section 5) ## Section 3.1 Should there be informative references for MELPe, G.729D ? Is this subsection useful ? This document is about RTP payload and this subsection is more fit for the SCIP endpoints themselves. But, I am neither a transport nor an application expert, so, feel free to keep this subsection. # NITS The official name of the UNO member state is "United States of America" and not simply "United States".
- [AVTCORE] Éric Vyncke's Discuss on draft-ietf-avt… Éric Vyncke via Datatracker
- Re: [AVTCORE] Éric Vyncke's Discuss on draft-ietf… Dan.Hanson@gd-ms.com
- Re: [AVTCORE] Éric Vyncke's Discuss on draft-ietf… Bernard Aboba
- Re: [AVTCORE] Éric Vyncke's Discuss on draft-ietf… Eric Vyncke (evyncke)
- Re: [AVTCORE] Éric Vyncke's Discuss on draft-ietf… Bernard Aboba
- Re: [AVTCORE] Éric Vyncke's Discuss on draft-ietf… Eric Vyncke (evyncke)
- Re: [AVTCORE] Éric Vyncke's Discuss on draft-ietf… Dan.Hanson@gd-ms.com
- Re: [AVTCORE] Éric Vyncke's Discuss on draft-ietf… Harald Alvestrand
- Re: [AVTCORE] Éric Vyncke's Discuss on draft-ietf… Eric Vyncke (evyncke)
- Re: [AVTCORE] Éric Vyncke's Discuss on draft-ietf… Dan.Hanson@gd-ms.com