IETF Logo Mail Archive

[Cellar] normative references

Michael Richardson <mcr+ietf@sandelman.ca> Mon, 26 September 2022 18:17 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 A2ACEC14CE25 for <cellar@ietfa.amsl.com>; Mon, 26 Sep 2022 11:17:17 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.908
X-Spam-Level:
X-Spam-Status: No, score=-1.908 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01, URIBL_ZEN_BLOCKED_OPENDNS=0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([50.223.129.194]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ia4GCDIsRXfu for <cellar@ietfa.amsl.com>; Mon, 26 Sep 2022 11:17:13 -0700 (PDT)
Received: from relay.sandelman.ca (relay.cooperix.net [IPv6:2a01:7e00:e000:2bb::1]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id C826CC14CF01 for <cellar@ietf.org>; Mon, 26 Sep 2022 11:17:13 -0700 (PDT)
Received: from dooku.sandelman.ca (unknown [89.246.252.107]) by relay.sandelman.ca (Postfix) with ESMTPS id D67AB1F489 for <cellar@ietf.org>; Mon, 26 Sep 2022 18:17:10 +0000 (UTC)
Received: by dooku.sandelman.ca (Postfix, from userid 179) id F1C951A074B; Mon, 26 Sep 2022 20:17:09 +0200 (CEST)
From: Michael Richardson <mcr+ietf@sandelman.ca>
To: cellar@ietf.org
X-Attribution: mcr
X-Mailer: MH-E 8.6+git; nmh 1.7.1; GNU Emacs 27.1
MIME-Version: 1.0
Content-Type: multipart/signed; boundary="=-=-="; micalg="pgp-sha512"; protocol="application/pgp-signature"
Date: Mon, 26 Sep 2022 20:17:09 +0200
Message-ID: <153671.1664216229@dooku>
Archived-At: <https://mailarchive.ietf.org/arch/msg/cellar/cJWSnkIB2yIaS1gw_n11opd1-7A>
Subject: [Cellar] normative references
X-BeenThere: cellar@ietf.org
X-Mailman-Version: 2.1.39
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: Mon, 26 Sep 2022 18:17:17 -0000

In the normative references, I see:

   [MatroskaCodec]
              Lhomme, S., Bunkus, M., and D. Rice, "Media Container
              Codec Specifications", Work in Progress, Internet-Draft,
              draft-ietf-cellar-codec-09, 12 April 2021,
              <https://datatracker.ietf.org/doc/html/draft-ietf-cellar-
              codec-09>.

   [MatroskaTags]
              Lhomme, S., Bunkus, M., and D. Rice, "Matroska Media
              Container Tag Specifications", Work in Progress, Internet-
              Draft, draft-ietf-cellar-tags-09, 12 April 2021,
              <https://datatracker.ietf.org/doc/html/draft-ietf-cellar-
              tags-09>.


This will cause the document to stall at MIS-REF until we finish those
documents.   Do they need to be *normative*?  Could I implement an encoder or
decoder without reading those documents?

Also, I wonder if the AES (FIPS.197), TwoFish, WebMEncryption,  need to be
normative references?



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

v2.23.0 | Report a Bug | By Email