[AVTCORE] Francesca Palombini's Discuss on draft-ietf-avtcore-rtp-scip-04: (with DISCUSS and COMMENT)

Francesca Palombini via Datatracker <noreply@ietf.org> Mon, 09 January 2023 14:24 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 819F7C153CAD; Mon, 9 Jan 2023 06:24:56 -0800 (PST)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: Francesca Palombini 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: 9.4.0
Auto-Submitted: auto-generated
Precedence: bulk
Reply-To: Francesca Palombini <francesca.palombini@ericsson.com>
Message-ID: <167327429651.3951.993767258989587096@ietfa.amsl.com>
Date: Mon, 09 Jan 2023 06:24:56 -0800
Archived-At: <https://mailarchive.ietf.org/arch/msg/avt/SlWW2g74Rl-_41MzsYBMR-sZT4o>
Subject: [AVTCORE] Francesca Palombini's Discuss on draft-ietf-avtcore-rtp-scip-04: (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: Mon, 09 Jan 2023 14:24:56 -0000

Francesca Palombini has entered the following ballot position for
draft-ietf-avtcore-rtp-scip-04: 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:
----------------------------------------------------------------------

Apologies for the delayed DISCUSS ballot. I just wanted to bring a process
question up before the document moves forward.

Since this document will be the reference RFC for two existing media type
registrations, I wonder if the change controller should be changed to IETF
instead of the SCIP wg. In practice this would mean that any change to the
registration would need to go through the IETF, which might make inconsistency
between the RFC of reference and the registrations less likely.


----------------------------------------------------------------------
COMMENT:
----------------------------------------------------------------------

Thank you for the work on this document. I also read this document without
reading the SCIP spec, as that spec is referenced informatively.

Many thanks to Jim Fenton for his ART ART reviews:
https://mailarchive.ietf.org/arch/msg/art/VUZVeNkbH40M6Oy_yqI7Om9Lvo0/ and
https://mailarchive.ietf.org/arch/msg/art/HjMttUhTSLuOJZvrvALfHHbAl90/, and to
the authors for addressing Jim's comments.