RFC 8446 mentions the cached-information extension from RFC 7924 in the context of the contents of the Certificate message, but does not list it in the ExtensionType enum or populate the "TLS 1.3" column in the registry.
From first look, its information is not needed for the TLS 1.3 key exchange and thus it could go in EncryptedExtensions.
It seems inconsistent to mention the extension as possibly modifying the Certificate message structure when there's not actually a formally defined way to use the extension for TLS 1.3
RFC 8446 mentions the cached-information extension from RFC 7924 in the context of the contents of the Certificate message, but does not list it in the ExtensionType enum or populate the "TLS 1.3" column in the registry. From first look, its information is not needed for the TLS 1.3 key exchange and thus it could go in EncryptedExtensions.
It seems inconsistent to mention the extension as possibly modifying the Certificate message structure when there's not actually a formally defined way to use the extension for TLS 1.3