[Enhancement] Add Interpret field
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 12.6k
- Forks
- 2.2k
- Avg merge
- 1d 4h
- Merged PRs (30d)
- 56
Description
Brief description
ERPS standard (probably some others) interpret lower layer's data.
For example, R-APS messages encode ERPS ring ID into MAC address:
The R-APS messages will use the MAC address range allocated within the ITU organizationally unique identifier (OUI) for [ITU-T G.8032] R-APS communication. The last octet of the MAC address is designated as ring ID (01-19-A7-00-00-[Ring ID]). The default ring ID is 01.
While this information resides in the lower layers, its interpretation logically belongs to the current layer. Some kind of Interpret field is needed to represent such data properly. It could inspect lower layers for information on dissection and patch data on build.
Scapy version
any
Python version
any
Operating system
any
Additional environment information
No response
How to reproduce
Actual result
No response
Expected result
No response
Related resources
No response
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
The issue does not identify files, tests, or an entry point. Start by reviewing Scapy's packet dissection and build behavior, then determine how lower-layer data could be interpreted and represented. Done would require an agreed design and implementation for the proposed Interpret field, including the R-APS ring ID example.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- networking
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100