Re: [AVTCORE] Zaheduzzaman Sarker's Discuss on draft-ietf-payload-rtp-jpegxs-16: (with DISCUSS)
"Murray S. Kucherawy" <superuser@gmail.com> Fri, 18 June 2021 15:50 UTC
Return-Path: <superuser@gmail.com>
X-Original-To: avt@ietfa.amsl.com
Delivered-To: avt@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id DEEC43A15DC; Fri, 18 Jun 2021 08:50:24 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.097
X-Spam-Level:
X-Spam-Status: No, score=-2.097 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 5mmXKzbtsirL; Fri, 18 Jun 2021 08:50:20 -0700 (PDT)
Received: from mail-ua1-x92c.google.com (mail-ua1-x92c.google.com [IPv6:2607:f8b0:4864:20::92c]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 77C3E3A15DB; Fri, 18 Jun 2021 08:50:19 -0700 (PDT)
Received: by mail-ua1-x92c.google.com with SMTP id r9so2212241ual.7; Fri, 18 Jun 2021 08:50:19 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=FrqG2jp5RykuiKx5fAslD0wogQK7cu2vWsmmcb5YMMk=; b=brrCrZtVtmxioh5xDkPH0gqQ8xugFJrQ8XeyJty0GRHpCcwa2CN0+9XEVEvVD87We2 Fm5iO/Z25NRlYJKXQfEEdj5ilmH0YaPcMzYkEUtfAHS8hVGEXTs/iC0ewVjPpyEjNvLV mDzxLHs3TsCejUFOzKPrVhdMAa0uuxVwwMTY0D4tDYgNtKVtJcMXBI6hMVSURHzw+lEx 9FIR6Y3t1pZ2D/mPksZKjXI/42jNYRixq5l5GqXVhg2EHEq9ysCYYwE4ck7DKPMfqkNy B1Cq9VrStaFxy1ybrz0S8DCI98hvG2ac4L9CTXhkmY7qhDriKKM8oJ8seELj4vyR9xSr Cvxw==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=FrqG2jp5RykuiKx5fAslD0wogQK7cu2vWsmmcb5YMMk=; b=MAd8773stgAo+n9CBIn8Xx4RzkhiYL4X7unuku4yx0RwGdN5vnk4d0zyhkPq9WR0OJ cbaMyGW1ya3juTTkygYkppr03KWFc3TupV0gFBuwGmuwRgqo62mVL8lf+pcLV988TNna 55KJI/0iXulAT+UCSravm2HZTEdlWZCfpPJwKbYUzSXdLZliWooTVNm44LeJizdnCTys BZ3nuD+4dw58RNYPxOBfq1QqbMWWWlWdn+sri4hy9NUspqBm4nWVuORYCExufSGTdiTq 5VNMsfHXwUWsHT4TZsi5/79XGDVUpWvAhIx3OtcSG71RepenT8t69NKTBhGBD6SVHlJ5 dDQw==
X-Gm-Message-State: AOAM5323XR1ClFSBAeFumCOaZSsTQhlPJZW81mxXTp5KEzF55h1UllF7 qcXGjGKbRyFmMzUqxy6m+ZfxSAfiCaF6WeEnl30=
X-Google-Smtp-Source: ABdhPJwqo95P8klTI2+Q5QpRY7224P2qNz43QP0YJ6rMcjBQ5WamY417SXrtKC9HBsBix7tT8kxrJC93MTThzHtkq1s=
X-Received: by 2002:ab0:7595:: with SMTP id q21mr12902276uap.87.1624031417574; Fri, 18 Jun 2021 08:50:17 -0700 (PDT)
MIME-Version: 1.0
References: <162394064058.25101.13977050966651147048@ietfa.amsl.com> <PR3P192MB0748786F52B08EB298516140AC0E9@PR3P192MB0748.EURP192.PROD.OUTLOOK.COM>
In-Reply-To: <PR3P192MB0748786F52B08EB298516140AC0E9@PR3P192MB0748.EURP192.PROD.OUTLOOK.COM>
From: "Murray S. Kucherawy" <superuser@gmail.com>
Date: Fri, 18 Jun 2021 08:50:05 -0700
Message-ID: <CAL0qLwZyFgA0XyMX=dX9=nbcOyhjcWBju0RLENbP993b7N+2Dw@mail.gmail.com>
To: Tim Bruylants <TBR@intopix.com>
Cc: Zaheduzzaman Sarker <Zaheduzzaman.Sarker@ericsson.com>, The IESG <iesg@ietf.org>, "draft-ietf-payload-rtp-jpegxs@ietf.org" <draft-ietf-payload-rtp-jpegxs@ietf.org>, "avtcore-chairs@ietf.org" <avtcore-chairs@ietf.org>, Ali Begen <ali.begen@networked.media>, "avt@ietf.org" <avt@ietf.org>, "bernard.aboba@gmail.com" <bernard.aboba@gmail.com>
Content-Type: multipart/alternative; boundary="000000000000bfa85405c50c4757"
Archived-At: <https://mailarchive.ietf.org/arch/msg/avt/GLuyWe3g0BiIIqg58XgAecg3Wck>
Subject: Re: [AVTCORE] Zaheduzzaman Sarker's Discuss on draft-ietf-payload-rtp-jpegxs-16: (with DISCUSS)
X-BeenThere: avt@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
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, 18 Jun 2021 15:50:25 -0000
On Thu, Jun 17, 2021 at 12:10 PM Tim Bruylants <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. > This is the first one like it in my time on the IESG, and I must admit I didn't even think to check that this external reference was usable. I'm glad Zaheduzzaman caught it. It might alleviate the problem to reduce this to an informative reference, but it doesn't look to me like you could make the argument that you don't need the ISO standards to implement this. You're not simply wrapping their protocol as-is; you need some header details, for example. I've asked the RFC Editor if they know of any documents that proceeded with closed references to ISO documents. If there are any, I'll review their processing history and see if I can find a path forward here. -MSK
- [AVTCORE] Zaheduzzaman Sarker's Discuss on draft-… Zaheduzzaman Sarker via Datatracker
- Re: [AVTCORE] Zaheduzzaman Sarker's Discuss on dr… Tim Bruylants
- Re: [AVTCORE] Zaheduzzaman Sarker's Discuss on dr… Stephan Wenger
- Re: [AVTCORE] Zaheduzzaman Sarker's Discuss on dr… Spencer Dawkins at IETF
- Re: [AVTCORE] Zaheduzzaman Sarker's Discuss on dr… Tim Bruylants
- Re: [AVTCORE] Zaheduzzaman Sarker's Discuss on dr… Stephan Wenger
- Re: [AVTCORE] Zaheduzzaman Sarker's Discuss on dr… Murray S. Kucherawy
- Re: [AVTCORE] Zaheduzzaman Sarker's Discuss on dr… Tim Bruylants
- Re: [AVTCORE] Zaheduzzaman Sarker's Discuss on dr… Stephan Wenger
- Re: [AVTCORE] Zaheduzzaman Sarker's Discuss on dr… Bernard Aboba
- Re: [AVTCORE] Zaheduzzaman Sarker's Discuss on dr… Keith Drage
- Re: [AVTCORE] Zaheduzzaman Sarker's Discuss on dr… Murray S. Kucherawy
- Re: [AVTCORE] Zaheduzzaman Sarker's Discuss on dr… Tim Bruylants
- Re: [AVTCORE] Zaheduzzaman Sarker's Discuss on dr… Thomas Richter
- Re: [AVTCORE] Zaheduzzaman Sarker's Discuss on dr… Stephan Wenger
- Re: [AVTCORE] Zaheduzzaman Sarker's Discuss on dr… Stephan Wenger
- Re: [AVTCORE] Zaheduzzaman Sarker's Discuss on dr… Tim Bruylants
- Re: [AVTCORE] Zaheduzzaman Sarker's Discuss on dr… Tim Bruylants
- Re: [AVTCORE] Zaheduzzaman Sarker's Discuss on dr… Zaheduzzaman Sarker