IETF Logo Mail Archive

Re: [Cellar] ffv1 missref status

Michael Richardson <mcr+ietf@sandelman.ca> Fri, 12 March 2021 21:15 UTC

Return-Path: <mcr@sandelman.ca>
X-Original-To: cellar@ietfa.amsl.com
Delivered-To: cellar@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id CDAF23A13BF for <cellar@ietfa.amsl.com>; Fri, 12 Mar 2021 13:15:26 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.232
X-Spam-Level:
X-Spam-Status: No, score=-1.232 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, KHOP_HELO_FCRDNS=0.001, SPF_HELO_NONE=0.001, SPF_SOFTFAIL=0.665, URIBL_BLOCKED=0.001] autolearn=no autolearn_force=no
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 MnmSXt2gF1LN for <cellar@ietfa.amsl.com>; Fri, 12 Mar 2021 13:15:19 -0800 (PST)
Received: from relay.sandelman.ca (minerva.sandelman.ca [IPv6:2a01:7e00::3d:b000]) (using TLSv1.2 with cipher ADH-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 248F13A13BD for <cellar@ietf.org>; Fri, 12 Mar 2021 13:15:19 -0800 (PST)
Received: from dooku.sandelman.ca (cpe788a207f397a-cmbc4dfb96bb50.sdns.net.rogers.com [174.116.121.43]) by relay.sandelman.ca (Postfix) with ESMTPS id 3BBAD1F44E; Fri, 12 Mar 2021 21:15:16 +0000 (UTC)
Received: by dooku.sandelman.ca (Postfix, from userid 179) id 4D7321A02B8; Fri, 12 Mar 2021 16:15:15 -0500 (EST)
From: Michael Richardson <mcr+ietf@sandelman.ca>
To: Codec Encoding for LossLess Archiving and Realtime transmission <cellar@ietf.org>
CC: Dave Rice <dave@dericed.com>
In-reply-to: <D113AC36-610D-49B5-BCEE-6FF497C4014F@dericed.com>
References: <D113AC36-610D-49B5-BCEE-6FF497C4014F@dericed.com>
Comments: In-reply-to Dave Rice <dave@dericed.com> message dated "Thu, 11 Mar 2021 15:32:04 -0500."
X-Mailer: MH-E 8.6+git; nmh 1.7.1; GNU Emacs 26.3
MIME-Version: 1.0
Content-Type: multipart/signed; boundary="=-=-="; micalg="pgp-sha512"; protocol="application/pgp-signature"
Date: Fri, 12 Mar 2021 16:15:15 -0500
Message-ID: <1478779.1615583715@dooku>
Archived-At: <https://mailarchive.ietf.org/arch/msg/cellar/8oOSvWq6cA2v7OEZZnqw2shBL_A>
Subject: Re: [Cellar] ffv1 missref status
X-BeenThere: cellar@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Codec Encoding for LossLess Archiving and Realtime transmission <cellar.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/cellar>, <mailto:cellar-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/cellar/>
List-Post: <mailto:cellar@ietf.org>
List-Help: <mailto:cellar-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/cellar>, <mailto:cellar-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 12 Mar 2021 21:15:27 -0000

Dave Rice <dave@dericed.com> wrote:
    > Hi Michael, Spencer, I see that FFV1 is in “RFC Ed Queue” status with
    > with “MISSREF for 8 days” which IIUC means that the RFC editor is
    > awaiting a missing normative reference.

Yeah.  I think we (chairs) screwed up here.

It seems that ffv1 has a normative reference to Matroska:

9.  Normative References

   [ISO.15444-1.2016]
              International Organization for Standardization,
              "Information technology -- JPEG 2000 image coding system:
              Core coding system", October 2016.

   [ISO.9899.2018]
              International Organization for Standardization,
              "Programming languages - C", ISO Standard 9899, 2018.

   [Matroska] IETF, "Matroska", 2019, <https://datatracker.ietf.org/doc/
              draft-ietf-cellar-matroska/>.


So we aren't allowed to normatively reference Internet Drafts.
It is referenced in section 4.3.3.4 only only.
I don't think it needs to be a normative reference.

Our choices are:
  1) leave things as they are, and finish Matroska faster.  FFV1 will
     wait for us in the Q.

  2) ask our AD to approve us changing this reference to informative.

My reading is that I don't think it needs to be normative.

--
Michael Richardson <mcr+IETF@sandelman.ca>, Sandelman Software Works
 -= IPv6 IoT consulting =-

v2.23.0 | Report a Bug | By Email