2. Gestion des numeros de manifeste

2. Gestion des numeros de manifeste

For a given CA, an RP MUST NOT reject a new manifest from that CA only because it does not have a higher manifestNumber than a previously validated manifest if the new manifest has a different filename. In other words, an RP resets its stored manifestNumber for a CA when the CA changes the filename of its manifest. This updates Section 4.2.1 of [RFC9286].

CAs SHOULD NOT use new manifest filenames except when such a change is needed to address the permanent invalidity problem described here. An RP MUST alert its operators when a manifest filename changes for a given CA.

RFC 9286 requires RPs to check both that a new manifest has a greater manifestNumber and that it has a more recent thisUpdate than the cached manifest. After a filename change, an RP momentarily omits the manifestNumber check, but replay protection remains if the RP still performs the thisUpdate check.