[Cellar] Re: [PATCH v2] ffv1: Support CRC with initial and final values not 0

Steve Lhomme <slhomme@matroska.org> Sun, 29 September 2024 07:30 UTC

Return-Path: <slhomme@matroska.org>
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 7F383C14F5F1 for <cellar@ietfa.amsl.com>; Sun, 29 Sep 2024 00:30:17 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.906
X-Spam-Level:
X-Spam-Status: No, score=-1.906 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, RCVD_IN_DNSWL_BLOCKED=0.001, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_HELO_NONE=0.001, SPF_NONE=0.001, T_SCC_BODY_TEXT_LINE=-0.01] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=matroska-org.20230601.gappssmtp.com
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 MBVqQEFdtzMK for <cellar@ietfa.amsl.com>; Sun, 29 Sep 2024 00:30:16 -0700 (PDT)
Received: from mail-wr1-x431.google.com (mail-wr1-x431.google.com [IPv6:2a00:1450:4864:20::431]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) key-exchange X25519 server-signature ECDSA (P-256) server-digest SHA256) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 52743C14F5E6 for <cellar@ietf.org>; Sun, 29 Sep 2024 00:30:15 -0700 (PDT)
Received: by mail-wr1-x431.google.com with SMTP id ffacd0b85a97d-37cea3a42ddso1256f8f.1 for <cellar@ietf.org>; Sun, 29 Sep 2024 00:30:15 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=matroska-org.20230601.gappssmtp.com; s=20230601; t=1727595014; x=1728199814; darn=ietf.org; h=to:references:message-id:content-transfer-encoding:cc:date :in-reply-to:from:subject:mime-version:from:to:cc:subject:date :message-id:reply-to; bh=uGdaf5u3fhq7caF6Pp6QzICFHqsY694hDoRDiNwj5jg=; b=UGZ712t/Sv4WhnHQSUHXnSM3DBjQP7RrtM2BO8ENpoWijoaK67afvyvJf5ayj/XocH wAUEKmrBg6oPvIe4B1kHyr/CNoEEba3Lk78TTloibYfknK6ii/f6HAWVuiPiUefdEvVw znLjumFbdb2T/IMguqVxctsiLzO1PpK6JaqmdP9OgKQV96atK1WtaBEcMzM+/Oxz/1wP VzuVuyBqLIL0N10gfVXn8d8nShwYAeDg6toxT2QQKdGrgXh2lwFLtMfy9wR/4p+5W5WE nkrnrzjEa0tUy/T4xaKgo69LGrzx21X/avaO9AkzkjZcjw4OWDERutmgfk0gir9VC8R5 3yqA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1727595014; x=1728199814; h=to:references:message-id:content-transfer-encoding:cc:date :in-reply-to:from:subject:mime-version:x-gm-message-state:from:to:cc :subject:date:message-id:reply-to; bh=uGdaf5u3fhq7caF6Pp6QzICFHqsY694hDoRDiNwj5jg=; b=mqgSOT6R5t+ZvKB6zorjwILwXxoxBkhg7RWlo8xHdpCGSqpXlvFeu1t+oR2fQjw3iA qjiEVHBp3RA0vBQicrJZyY+IADWwkV3t99kR0+kHTrHfk2KSkrBkjm3DkSxJVhFjMqPz yNR4A8XgtUzKwRnGo1IcTv72xFamAR10y741I2KPgOJ0ZEZ+Zo3IdQnRrBuUeB0mWyz3 C68ihJDT9bQLopTySqCySbEuBtUTcPv5WLDQ3bHJg4Sw7SU8fFaAAgdbEx+/ZcU9ZQ7M E2P35MpufwAxPn18+RTlTIjEodu+2yc4PEhBn017viKqnE/8QcOiO9+NaC9P/7RCVXjd 3oqw==
X-Gm-Message-State: AOJu0YwXt636WWDe9tz2q3x4Hw4HgSMd2lcbZYbedrN++mSBnJZQ3VUz 2+IoPoxnaNBkU67kmk5BFw34UXK866JdNa3MKhYv5f1WrF3O+1I2tj5XITvFEw==
X-Google-Smtp-Source: AGHT+IGm4bOyKpxSYPgTjnrE/1SJQzqUQlzNQH8Pnvw5F9Z0jC9Xx50O2g88cYQ/C9S4OdUwfJCP0w==
X-Received: by 2002:a05:6000:2a2:b0:378:9560:330 with SMTP id ffacd0b85a97d-37cde44b498mr1172906f8f.13.1727595013782; Sun, 29 Sep 2024 00:30:13 -0700 (PDT)
Received: from smtpclient.apple (2a01cb0c0e9dac006c8603bbbb8e58da.ipv6.abo.wanadoo.fr. [2a01:cb0c:e9d:ac00:6c86:3bb:bb8e:58da]) by smtp.gmail.com with ESMTPSA id ffacd0b85a97d-37cd572fbebsm6265108f8f.72.2024.09.29.00.30.12 (version=TLS1_2 cipher=ECDHE-ECDSA-AES128-GCM-SHA256 bits=128/128); Sun, 29 Sep 2024 00:30:13 -0700 (PDT)
Content-Type: text/plain; charset="utf-8"
Mime-Version: 1.0 (Mac OS X Mail 16.0 \(3776.700.51\))
From: Steve Lhomme <slhomme@matroska.org>
In-Reply-To: <20240928204122.GG4917@pb2>
Date: Sun, 29 Sep 2024 09:30:02 +0200
Content-Transfer-Encoding: quoted-printable
Message-Id: <59DEA005-7662-4AA1-8D98-B02339879A2B@matroska.org>
References: <20240926194313.684278-1-michael@niedermayer.cc> <D0A438D8-D25C-4064-9DD3-9FBDF9404686@matroska.org> <20240928204122.GG4917@pb2>
To: Michael Niedermayer <michael@niedermayer.cc>
X-Mailer: Apple Mail (2.3776.700.51)
Message-ID-Hash: MRBFMFXPW3YLY6DDC2OFRJKSNACHOI6J
X-Message-ID-Hash: MRBFMFXPW3YLY6DDC2OFRJKSNACHOI6J
X-MailFrom: slhomme@matroska.org
X-Mailman-Rule-Misses: dmarc-mitigation; no-senders; approved; emergency; loop; banned-address; member-moderation; header-match-cellar.ietf.org-0; nonmember-moderation; administrivia; implicit-dest; max-recipients; max-size; news-moderation; no-subject; digests; suspicious-header
CC: Codec Encoding for LossLess Archiving and Realtime transmission <cellar@ietf.org>
X-Mailman-Version: 3.3.9rc4
Precedence: list
Subject: [Cellar] Re: [PATCH v2] ffv1: Support CRC with initial and final values not 0
List-Id: Codec Encoding for LossLess Archiving and Realtime transmission <cellar.ietf.org>
Archived-At: <https://mailarchive.ietf.org/arch/msg/cellar/rw-Zt22GRmuvsdDI5_zRBNTF7Bs>
List-Archive: <https://mailarchive.ietf.org/arch/browse/cellar>
List-Help: <mailto:cellar-request@ietf.org?subject=help>
List-Owner: <mailto:cellar-owner@ietf.org>
List-Post: <mailto:cellar@ietf.org>
List-Subscribe: <mailto:cellar-join@ietf.org>
List-Unsubscribe: <mailto:cellar-leave@ietf.org>

Hi Michael,

> On 28 Sep 2024, at 22:41, Michael Niedermayer <michael@niedermayer.cc> wrote:
> 
> Hi Steve
> 
> On Sat, Sep 28, 2024 at 08:45:59AM +0200, Steve Lhomme wrote:
>> Hi Michael,
>> 
>> Given RFC 9043 is published and this seems like an addition to the format, it would probably needs its own document to introduce this new bit handling. Hopefully it’s backward compatible so it’s a no brainer. I don’t think it can be an errata, but you may try that.
> 
> RFC 9043 is about version 0, 1, and 3.
> we are of course discussing about version 4.

OK, no problem then.

> The hunk in the patch was missing the tag for V4, it should have been:
> 
> @@ -1267,7 +1267,8 @@ Figure: Description of the coding of `initial_state_delta[ i ][ j ][ k ]`. {#fig
> |value | error detection/correction type           |
> |------|:------------------------------------------|
> |0     | 32-bit CRC in `ConfigurationRecord`       |
> -|1     | 32-bit CRC in `Slice` and `ConfigurationRecord`|
> +|1     | 32-bit CRC in `Slice` and `ConfigurationRecord` using crcref=0  as initial and final values|
> +|2     | 32-bit CRC in `Slice` and `ConfigurationRecord` using crcref=0x7a8c4079 as initial and final values|{V4}
> |Other | reserved for future use                   |
> Table: The definitions for `ec` values. {#tableEc}
> 
> About compatible. As its written ATM in teh patch there is nothing an encoder
> needs to do differently, the old variant would still be valid.
> 
> On  the decoder side a old decoder would not know what to do with the
> error detection type=2. So if it ignores it it might decode things ok but
> more likely it will fail without trying
> 
> I think we can expect that most new features that will be in v4 will need a
> decoder thats aware of v4. another example will be floating point pixel formats

Indeed. The text change you propose doesn’t make it clear that this value should only be used (MUST or SHALL in IETF terms) if the bitstream is marked as FFV1 v4 or above. I assume that should be the same for other new features as well.

> thx
> 
> [...]
> -- 
> Michael     GnuPG fingerprint: 9FF2128B147EF6730BADF133611EC787040B0FAB
> 
> Never trust a computer, one day, it may think you are the virus. -- Compn
> _______________________________________________
> Cellar mailing list -- cellar@ietf.org
> To unsubscribe send an email to cellar-leave@ietf.org