Re: [AVTCORE] Zaheduzzaman Sarker's Discuss on draft-ietf-payload-rtp-jpegxs-16: (with DISCUSS)

As a follow-up, I had conversations with Mayumi and with Gary Sullivan (SC29 chair).  We are still checking if and how we can make 21122 available to the WG, and I will come back to you on this, hopefully early next week.
Stephan

From: avt <avt-bounces@ietf.org> on behalf of Stephan Wenger <stewe@stewe.org>
Date: Thursday, June 17, 2021 at 12:48
To: Tim Bruylants <TBR@intopix.com>, Zaheduzzaman Sarker <Zaheduzzaman.Sarker@ericsson.com>, The IESG <iesg@ietf.org>, Mayumi Koike <koike@itscj.ipsj.or.jp>
Cc: "draft-ietf-payload-rtp-jpegxs@ietf.org" <draft-ietf-payload-rtp-jpegxs@ietf.org>, "avtcore-chairs@ietf.org" <avtcore-chairs@ietf.org>, "avt@ietf.org" <avt@ietf.org>
Subject: Re: [AVTCORE] Zaheduzzaman Sarker's Discuss on draft-ietf-payload-rtp-jpegxs-16: (with DISCUSS)

Hi,

Copying Mayumi Koike, SC29 committee manager.

I'm sending this wearing my hat as the IETF's liaison to ISO/IEC JTC1/SC29, which includes SC29's WG1 JPEG.

It is my understanding that ISO documents can be shared in a liaison relationship, which we have here.  The IETF is a cat A liaison organization to SC29.  According to the ISO Directives (2021) (https://www.iso.org/sites/directives/current/consolidated/index.xhtml#_idTextAnchor095), section 1.17.2, subclause Category A, "[...] Such organizations are given access to all relevant documentation [...]".

Mayumi, can you please confirm?  For context, an RTP payload format for JPEG-XS under standardization in the IETF faces a hurdle in the approval process as it normatively references ISO/IEC 21122 and its subparts, and cannot be properly evaluated without having that ISO spec available.  What would be the easiest way to provide the IETF’s AVT WG with an appropriate copy?

Thanks,

Stephan

On 6/17/21, 12:10, "avt on behalf of Tim Bruylants" <avt-bounces@ietf.org on behalf of TBR@intopix.com> wrote:

    > ----------------------------------------------------------------------

    > DISCUSS:

    > ----------------------------------------------------------------------

    >

    > This memo is defining a RTP payload for JPEG XS that is not publicly available.

    > This hampers the review of the memo, specially when it is defining terminologies which ask me to look at the specifications.

    >

    > This concerns has also been raised by other ADs.

    >

    > Was this document made available during the work in the working group?

    This is a valid comment. We are unsure how to resolve this. ISO is very strict about distribution of documents outside of the working groups (i.e. it is not allowed at all).

    The ISO 21122 standards were written by some of the same authors as this RTP Payload spec (like myself and Thomas Richter), but the ISO documents were (to my knowledge) not shared.

    In order to resolve this issue, we need to know how IESG handled this with other ISO standards that are not open? Or is 21122 the first? Please advise.

    _______________________________________________

    Audio/Video Transport Core Maintenance

    avt@ietf.org

    https://www.ietf.org/mailman/listinfo/avt