Opened 6 years ago

Last modified 3 years ago

#6597 enhancement new

IPv6 address literals support for IReactorMulticast.listenMulticast, IMulticastTransport.joinGroup, IMulticastTransport.joinGroup and others

Reported by: Martin Gergov Owned by:
Priority: normal Milestone:
Component: core Keywords:
Cc: Branch:
Author:

Description

In correlation with #5086 and #5087, support for ipv6 literals in udp multicast should be added.

Note that all methods from the public API in MulticastMixin have to accept options for IPv6.

Change History (2)

comment:1 in reply to:  description Changed 4 years ago by Darko

What's the state of this ticket? Can '.joinGroup' accepts IPv6 addresses now?

comment:2 Changed 3 years ago by Jason Litzinger

As a result of some mailing list discussion, I'm capturing a current plan of record for addressing joinGroup here.

  1. Internally, avoid modifications related to IPv6 for twisted.internet.base's resolve method to solve this problem. Resolution for IPv6 requires a more thorough approach. A ticket for resolution is here: https://twistedmatrix.com/trac/ticket/4362
  1. In joinGroup, use the addressFamily attribute to determine whether to follow the existing code path or execute the new IPv6 code.
  1. Preserve the existing api, which will for clients to ensure the interface parameter is a valid IPv6 address: self.transport.joinGroup("ff02::1", interface="::")

Or such is the current plan, which, like all, could change to suit the best result.

Relevant postings

http://twistedmatrix.com/pipermail/twisted-python/2016-July/030637.html

http://twistedmatrix.com/pipermail/twisted-python/2016-July/030642.html

http://twistedmatrix.com/pipermail/twisted-python/2016-July/030654.html

http://twistedmatrix.com/pipermail/twisted-python/2016-July/030656.html

Note: See TracTickets for help on using tickets.