[rtcweb] Paul Wouters' No Objection on draft-uberti-rtcweb-rfc8829bis-03: (with COMMENT)

Paul Wouters via Datatracker <noreply@ietf.org> Thu, 06 October 2022 00:30 UTC

Return-Path: <noreply@ietf.org>
X-Original-To: rtcweb@ietf.org
Delivered-To: rtcweb@ietfa.amsl.com
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 1083CC1522A2; Wed, 5 Oct 2022 17:30:01 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: Paul Wouters via Datatracker <noreply@ietf.org>
To: The IESG <iesg@ietf.org>
Cc: draft-uberti-rtcweb-rfc8829bis@ietf.org, rtcweb-chairs@ietf.org, rtcweb@ietf.org, sean@sn3rd.com, sean@sn3rd.com
X-Test-IDTracker: no
X-IETF-IDTracker: 8.17.0
Auto-Submitted: auto-generated
Precedence: bulk
Reply-To: Paul Wouters <paul.wouters@aiven.io>
Message-ID: <166501620106.32401.9387471631161055766@ietfa.amsl.com>
Date: Wed, 05 Oct 2022 17:30:01 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/rtcweb/VetDrIDmLEgIm5lw_LmjVAJfxFs>
Subject: [rtcweb] Paul Wouters' No Objection on draft-uberti-rtcweb-rfc8829bis-03: (with COMMENT)
X-BeenThere: rtcweb@ietf.org
X-Mailman-Version: 2.1.39
List-Id: Real-Time Communication in WEB-browsers working group list <rtcweb.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/rtcweb>, <mailto:rtcweb-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/rtcweb/>
List-Post: <mailto:rtcweb@ietf.org>
List-Help: <mailto:rtcweb-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/rtcweb>, <mailto:rtcweb-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 06 Oct 2022 00:30:01 -0000

Paul Wouters has entered the following ballot position for
draft-uberti-rtcweb-rfc8829bis-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/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-uberti-rtcweb-rfc8829bis/



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

Some minor comments that are likely my misunderstanding of the protocol:

Section 3.5.2.1:

        Implementations MUST be prepared to receive objects with some fields
        missing, as mentioned above.

What does it mean to be "prepared"? Is there any guidance to give here ?

Section 5.2.1:

        The <sess-id> MUST be representable by a 64-bit signed integer,
        and the value MUST be less than 2^63-1.

Why is this a _signed_ integer and not an unsigned integer? What is the meaning
of 2^63-1 in a 64 bit signed integer ?

        [...] SHOULD NOT be included.

        [...] MUST NOT be included.

Should these be extended to say "MUST be ignored when received" ? Or is there
specific action that should take place that can be specified here?

NITS:

        opaque blobs; that is, the application will not need to read or
        change them.

maybe:

        opaque blobs; that is, the application will not need to parse or
        modify these.

("read" is a little ambiguous, it might need to memcpy (read and write) it,
but not grok it)

we could easily enable -> it could easily enable