You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hi, since the Draft 16 April 2024, the status_size property has been moved from BistringStatusList to BistringStatusListEntry. I understand it is sometimes necessary to know the status size from the entry without having to fetch the entire list, but removing it entirely from BitstringStatusList introduces some major issues in my opinion:
It is now impossible to decode a status list without possessing a status list entry.
The status size parameter must be passed around in many places of the implementation, making it error prone.
This differs from IETF Token Status Lists, making it hard to implement a common API.
The text was updated successfully, but these errors were encountered:
msporny
added
normative
The item is normative in nature.
CR1
This item was processed during the first Candidate Recommendation phase.
labels
Sep 16, 2024
Hi, since the Draft 16 April 2024, the
status_size
property has been moved fromBistringStatusList
toBistringStatusListEntry
. I understand it is sometimes necessary to know the status size from the entry without having to fetch the entire list, but removing it entirely fromBitstringStatusList
introduces some major issues in my opinion:The text was updated successfully, but these errors were encountered: