-
Notifications
You must be signed in to change notification settings - Fork 34
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
LICH contents reassembly #131
Comments
I see why the desire for having a different name due to the changing data and multiple uses. So we have:
I'm clear on the distinction between LSD and LSF (good luck qyslexics! I think I'd have to write each out a lot to keep them straight). I'm not fully clear on the distinction between LICH and LSD. |
Starting with LSD: |
Gotcha. If I have that right then each of these should be correct: LICH refers specifically to the chunks of LSD. So we're being more precise with the language. I like it, makes sense. |
Exactly. It makes little sense to say "recover full LSF" as LSF is a frame, not its contents. Or "LSF has to remain the same over the course of a single superframe" - again, LSF is a frame and not the data it holds. |
Link Setup Data* must remain the same over the course of a superframe, and receivers should only reassemble the LSD chunks from within a single superframe.
*naming convention - LSF is the first frame containing LSD. LSD is then also the data reassembled using LICH. Logically, it's not LSF.
The text was updated successfully, but these errors were encountered: