Skip to content
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

TO-DO Improvements #2

Open
8 of 17 tasks
pedrofran12 opened this issue Sep 9, 2019 · 0 comments
Open
8 of 17 tasks

TO-DO Improvements #2

pedrofran12 opened this issue Sep 9, 2019 · 0 comments
Assignees
Labels
enhancement New feature or request

Comments

@pedrofran12
Copy link
Owner

pedrofran12 commented Sep 9, 2019

This issue lists some ideas and future improvements that could be performed to HPIM-DM implementation/specification.

  • Relax the interest storage requirement of Assert Losers. Requires updating the specification.
  • BFD support?
  • Multiple physical interfaces of the same router directly connected to the source. If these interfaces are not a LAG there is the possibility of a loop (one interface considered root and the other(s) non-root -> which may cause data packets to be forwarded again to the source subnet by the non-root interface). Check specification and implementation if there is no issue (DONE Source link loop prevention #6).
  • Security -> Implement control message integrity & authentication check (DONE Security #3).
  • IGMPv3 and MLDv2.
  • IPv6 multicast routing support (update Kernel and implement MLD). (DONE IPv6 multicast routing support #7)
  • Option to ignore the Feasibility Condition in determining the tree state. This may be useful in sub-topologies where it is impossible to form a network loop and in which there are different routing protocols being used (ex: all routers use OSPF but a subset uses default static routes).
  • All code should be in hpimdm package (in order to allow hpim-dm and pim-dm implementations to coexist). (DONE Move all code to package hpimdm #4)
  • More automation on tests.
  • Forwarding state of a non-root interface that was AW should be preserved for a given amount of time to prevent loss of data packets when the AW changes. (DONE Hold forwarding state assert #5)
  • Better debug messages.
  • Try to remove tcpdump dependency (manually create BPF filter bytecode).
  • Change API used to access unicast routing information (ipdb will become deprecated).
  • Perform tests using other environment (current one does not have support for IPv6 multicast routing - limitations at the kernel level).
  • Multiple tables support. (DONE)
  • Have a configuration file to configure everything on startup.(DONE)
  • Multicast routing protocol takes into consideration interest of own router (router has application that joined some multicast groups)
@pedrofran12 pedrofran12 self-assigned this Sep 9, 2019
pedrofran12 added a commit that referenced this issue Sep 11, 2019
@pedrofran12 pedrofran12 mentioned this issue Sep 11, 2019
@pedrofran12 pedrofran12 pinned this issue Sep 19, 2019
pedrofran12 added a commit that referenced this issue Feb 6, 2020
* Implement timer to hold forwarding state when current assert winner loses assert

* fix verification of forwarding state on hold (check thread id)

* Include -hfs in README
Repository owner locked and limited conversation to collaborators Feb 8, 2020
@pedrofran12 pedrofran12 added the enhancement New feature or request label Apr 11, 2020
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

1 participant