[art] Artart last call review of draft-ietf-avtcore-rfc7983bis-07

Marc Blanchet via Datatracker <noreply@ietf.org> Mon, 09 January 2023 16:11 UTC

Return-Path: <noreply@ietf.org>
X-Original-To: art@ietf.org
Delivered-To: art@ietfa.amsl.com
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 87B6CC1CCC8B; Mon, 9 Jan 2023 08:11:02 -0800 (PST)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: Marc Blanchet via Datatracker <noreply@ietf.org>
To: art@ietf.org
Cc: avt@ietf.org, draft-ietf-avtcore-rfc7983bis.all@ietf.org, last-call@ietf.org
X-Test-IDTracker: no
X-IETF-IDTracker: 9.4.0
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <167328066254.3749.18439149944819935858@ietfa.amsl.com>
Reply-To: Marc Blanchet <Marc.Blanchet@viagenie.ca>
Date: Mon, 09 Jan 2023 08:11:02 -0800
Archived-At: <https://mailarchive.ietf.org/arch/msg/art/6XD3ODz8YPo4ps6yIIe1BgQnZNI>
Subject: [art] Artart last call review of draft-ietf-avtcore-rfc7983bis-07
X-BeenThere: art@ietf.org
X-Mailman-Version: 2.1.39
List-Id: Applications and Real-Time Area Discussion <art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/art>, <mailto:art-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/art/>
List-Post: <mailto:art@ietf.org>
List-Help: <mailto:art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/art>, <mailto:art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 09 Jan 2023 16:11:02 -0000

Reviewer: Marc Blanchet
Review result: Ready

I have reviewed version -07. I did not read the identified references, so I
can't tell if the various code points cited are right or that the specification
is correct or not, but I found the document clear and makes sense, given that
source IP address and port will be different for QUIC compared to TURN so it
could be demultiplexed. I used to be on i18n directorate (which merged into
ART) to review i18n related issues, so, on that topic, I see no i18n issues at
all.

One possible nit (English is not my native language):
s/Were SRTP to be/Where SRTP to be/