Skip to content

Handle new-initiator/new-responder correctly #61

@lgrahl

Description

@lgrahl

When a 'new-initiator' or 'new-responder' message has been received, the initiator/responder simply replaces the corresponding instance but does not reset its own state.

Due to a limitation of the implementation, after the task has kicked in, it should also...

  • drop the responder in case it is an initiator, and
  • close the connection normally in case it is a responder.

Metadata

Metadata

Assignees

No one assigned

    Labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions