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
In the meeting on 2022-10-12, there was mention of needing to say which choices were made in generating the hash.
We already have the existing URDNA2015 as the canonicalization algorithm. Anything this working group does that makes any change to that will need to have a way to declare which algorithm was used to produce the resultant canonical form.
There may be good reasons for different hashing and signing algorithms.
We need a naming scheme of choices made, together with a way to transmit that information.
I think it's the responsibility of a container format to express hashing, signing, and canonicalization algorithm choices. It's our responsibility here to provide a name for the canonicalization algorithm, which will be done when issue #87 is closed. I recommend we close this issue on that basis.
In the meeting on 2022-10-12, there was mention of needing to say which choices were made in generating the hash.
We already have the existing URDNA2015 as the canonicalization algorithm. Anything this working group does that makes any change to that will need to have a way to declare which algorithm was used to produce the resultant canonical form.
There may be good reasons for different hashing and signing algorithms.
We need a naming scheme of choices made, together with a way to transmit that information.
See #4 about the output of canonicalization.
The text was updated successfully, but these errors were encountered: