Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Fields size inconsistency in OVIP-2 and OVIP-7 #20

Open
starkmsu opened this issue Jul 16, 2020 · 0 comments
Open

Fields size inconsistency in OVIP-2 and OVIP-7 #20

starkmsu opened this issue Jul 16, 2020 · 0 comments

Comments

@starkmsu
Copy link

In OVIP-7 , part 2.2.1 stated:

Sender | sender | Hex(32-bit) | VASP Identifier of the Sender
Receiver | receiver | Hex(32-bit) | VASP Identifier of the Receiver

But in OVIP-2 (part 2.1.6) the definition of VASP Identifier is the following:
The VASP Identfier is the implicit combination of the VASP Code Type, the two Reserved Bits and the VASP Code. It uniquely, globally identifies a VASP. It is, in other words, the first 12 hexadecimal characters of a VAAN.

So based on OVIP-2 VASP Identifier must have a length of 48-bit, but in OVIP-7 it's specified that it has a length of 32-bit.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant