HIPLv2: Duality of version number
Bug #913516 reported by
Tobias Heer
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| HIPL |
In Progress
|
Undecided
|
Xin | ||
Bug Description
HIPv2 uses a different version number. I assume you try to createe a HIPv1 and HIPv2 dual stack implementation (makes most sense) . Therefore, the HIP version of a packet and of an association must be availabe within the processing functions.
a) Store the HIP version for an association based on the BEX packets.
b) Check for the right version for packets that belong to an existing association.
c) Make the version accessible for handler functions in a clean way
Revision history for this message
| Miika Komu (miika-iki) wrote | #1 |
| Changed in hipl: | |
| assignee: | nobody → Xin (eric-nevup) |
| Changed in hipl: | |
| status: | New → In Progress |
To post a comment you must log in.
I would actually suggest to exclude support for HIPv1 altogether but let's discuss.