new config for ipv6 related changes

[shotasilagadzetaal]

Description of Changes

New config parameters for ipv6 related changes

Linked Issues / Tickets

Closes #ARCO-229

Testing Procedure

I have added test case to check if all the values are correctly read from config

Checklist:

• I have performed a self-review of my own code
• I have made corresponding changes to the documentation
• My changes generate no new warnings
• I have updated CHANGELOG.md with my changes

[kuba-4chain]

Nice work. I just have a question, because maybe I'm missing something, this config is a preparation for further changes to implement the IPv6 communications, but for now it's not yet being used anywhere, right?

[arkadiuszos4chain]

I see two potential approaches:

1. Use P2P for Multicasting

Not my preferred option, but workable.

• Update the PeerConfig structure as follows:

  Peer:
    mode: unicast | multicast
    address | host: url
    port: number
  

• Explanation:
  • if mode is unicast, the peer operates as it currently does, with no additional changes
  • if mode is multicast, the url must be an IPv6 multicast group address

2. Implement a Multicast Handler (that works alongside P2P)

• This handler would have similar logic to the peer but be simpler (no reconnections, no ping-pong messages, no handshakes).

• Add a new configuration key:

  broadcast | network-communication:
    Peers: []           # (optional) same as current setup
    Multicast:
      group: url
      port: number      # (optional)
      

• Currently, it is unclear how groups would function in the network. Possible options include:

  • using a single multicast group with different ports to handle distinct topics
  • using a separate multicast group per topic
    therefore, the final schema of Multicast could change.

I believe that go-p2p is agnostic regarding IP version, so there is no need to introduce the IPv6enabled flag.

[shotasilagadzetaal]

Nice work. I just have a question, because maybe I'm missing something, this config is a preparation for further changes to implement the IPv6 communications, but for now it's not yet being used anywhere, right?

yeap, exactly

[boecklim]

nit: This can be removed I think

[sonarcloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
100.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarCloud