crc checksum input

[sschulz-t]

Regarding

openid4vp_ble/main.md

Line 344 in e5370d5

**Checksum:** 2 bytes CRC16-CCITT-False (unsigned)

In this case i assume the input is the chunk num and chunk data, however the specification should specify it clearly that no assumptions are needed.

[gsasikumar]

I thought the table was providing the clarity. But I agree we can make this change to provide better clarity. I will open a PR on the same by tomorrow.

[sschulz-t]

I think this should be written more precise. I was looking at this:

openid4vp_ble/main.md

Lines 336 to 344 in e5370d5

	| Chunk sequence no | Chunk payload | Checksum value of data |
	|-----------------------|-------------------------------------|---------------------------|
	| (2 bytes) | (upto MTU-4 bytes - 2 bytes) | (2 bytes) |
	**Chunk Sequence No:** Running unsigned counter for the chunk and starts with 1 (Max 65535)
	**Chunk Payload:** Chunk data.
	**Checksum:** 2 bytes CRC16-CCITT-False (unsigned)

The table says checksum of "data" and the text below the table specifies chunk payload as chunk data. One could easily misinterpret this and not include the seqNo in the crc.

I can work out a revised definition and create a PR if you want.

[gsasikumar]

@sschulz-t Yes it would be great if you can.