Attention is currently required from: laforge.
1 comment:
File pySim/esim/saip/__init__.py:
can't we deduct the SCP02/03/80 usage from the KVN? And then determine the length based on that? If […]
As far as I can see there is only one length per SCP: 5 bytes for SCP80, 3 for SCP03 and 2 for
SCP02, the same as the defaults in SAIP 8.6.3. So yes, the length could come from the KVN ranges
in that table.
Two corner cases I'd like to align on before I upload the next patch set:
- A counter on a KVN outside those ranges (the table says it's incomplete): should that raise, or
would you allow an optional explicit length there?
- A decoded counter whose length doesn't match its KVN: keep the decoded length, so decode and
re-encode stay byte-identical, or re-encode with the length the KVN implies?
What would you prefer?
To view, visit change 44011. To unsubscribe, or for help writing mail filters, visit settings.