CN103095585B - The method and system of multicast control stream information intercommunication between a kind of IPv4 and IPv6 - Google Patents
The method and system of multicast control stream information intercommunication between a kind of IPv4 and IPv6 Download PDFInfo
- Publication number
- CN103095585B CN103095585B CN201110341730.4A CN201110341730A CN103095585B CN 103095585 B CN103095585 B CN 103095585B CN 201110341730 A CN201110341730 A CN 201110341730A CN 103095585 B CN103095585 B CN 103095585B
- Authority
- CN
- China
- Prior art keywords
- ipv4
- ipv6
- message
- multicast
- control stream
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Active
Links
Abstract
The invention discloses the method and systems that multicast between a kind of IPv4 and IPv6 controls stream information intercommunication, including：When connection equipment receives the control stream packet of IPv4 multicast domains, the control stream packet for generating corresponding IPv6 multicast domains is sent to IPv6 multicast domains；When connection equipment receives the control stream packet of IPv6 multicast domains, the control stream packet for generating corresponding IPv4 multicast domains is sent to IPv4 multicast domains.It can solve the problem of that multicast caused by being mismatched due to the address family that multicast source, multicast recipient and transmission network are run in the migration course of IPv4 to IPv6 is difficult to carry out through the invention.
Description
Technical field
The present invention relates to the communications field, the method that particularly relates to multicast control stream information intercommunication between a kind of IPv4 and IPv6
And system.
Background technology
In current deployment, service provider provides some services using IP multicast forwarding mechanism, as live telecast takes
Business etc..In network into IPv6 migration courses, IP multicasts also proposed many new demands while encountering many problems.From
From the perspective of business, the continuity of IPv4 services is an important demand, and particular content includes：One can not possibly transferred the possession of
The special addresses global ip v4 have been moved to multicast receivers or multicast receivers under the scene of IPv6 networks, still to be allowed
Multicast receivers continue to access the content of IPv4-formatted.Similarly, the content of IPv6-formatted is also required to
It is transmitted to IPv4 multicast receivers.In the case where transmission network and multicast source or multicast receivers support different address race,
This continuity remains able to ensure the transmission of multicast packet.
In the evolution stage of IPv4 to IPv6, multicast receivers, multicast source and multicast network may run different
Address family, but at the same time, service provider must assure that is delivered to IPv4 multicast receivers or IPv6 by multicast services
Multicast receivers.Generally speaking, there are following four situations：
1, pass through the IPv4 multicast sources of IPv6-only network connections and IPv4 multicast receivers.
This scene may be summarized to be 4-6-4, be represented as DS-lite, the CPE that user passes through an imparting IPv6 prefix
Access, and the shared addresses global ip v4 are communicated with server.In this case, IPv4 multicast sources send multicast content
To some interworking function of IPv4 recipients demand.The flow of multicast can be encapsulation or translation.Divide from existing research
Analysis, this scene is the case where service provider's preecedence requirement considers, in the evolution to IPv6, client and service provider
The some time is often in the IPv4-formatted stages.
2, pass through the IPv6 multicast sources of IPv4-only network connections and IPv6 multicast receivers.
This scene may be summarized to be 6-4-6.According to the analysis of BEHAVE working groups, move to IPv6's in unicast data
In the process, service provider is possible to be still IPv4-enabled.Multicast migration is equally also set up in this analysis.
3, IPv6 multicast receivers and IPv4 multicast sources.
This scene may be summarized to be 6-4.It is embodied in some mobile networks, terminal device is IPv6-
The equipment of only needs to realize the multicast under this scene when these equipment want the content of access IPv4-formatted
Function.
4, IPv4 multicast receivers and IPv6 multicast sources.
This scene may be summarized to be 4-6.In the later stage for mainly appearing on IP migrations, IPv6 is all adjourned in most of network
When, still there is small part user to remain as IPv4-only, needs to ensure that these IPv4-only users can be from IPv6 multicast sources
Obtain multicast packet.
It can be seen that in the four kinds of scenes analyzed above, the IPv6 multicast services constantly introduced can cause multicast to be delivered
Mismatch between the address family of certain parts of facility, mainly between multicast receivers, multicast source and transmission network.This
It is that and IPv4 multicast packet different from multicast protocol used in IPv6 and IPv6 multicast packets formats are different and cause due to IPv4
's.In multicast control stream, IPv4 uses IGMP and PIMv4 agreements, and IPv6 uses MLD and PIMv6 agreements；In multicast packet
In stream, IPv4 and IPv6 is different to the format of multicast packet, when needing a group sowing time between the domains IPv4 and the domains IPv6, due to address family
Mismatch so that multicast is difficult to carry out.Therefore in the migration course of IPv4 to IPv6, it would be desirable to introduce an IPv4 and
Multicast interworking function between IPv6.
Invention content
In view of this, the main purpose of the present invention is to provide multicasts between a kind of IPv4 and IPv6 to control stream information intercommunication
Method and system, can solve in the migration course of IPv4 to IPv6, due to multicast source, multicast recipient and transmission network
The problem of multicast caused by the address family of operation mismatches is difficult to carry out.
In order to achieve the above objectives, the technical proposal of the invention is realized in this way：
The present invention provides between a kind of IPv4 and IPv6 multicast control stream information intercommunication method,
When connection equipment receives the control stream packet of IPv4 multicast domains, the control stream report of corresponding IPv6 multicast domains is generated
Text is sent to IPv6 multicast domains；
When connection equipment receives the control stream packet of IPv6 multicast domains, the control stream report of corresponding IPv4 multicast domains is generated
Text is sent to IPv4 multicast domains.
Wherein, when IPv4 multicast domains use MLD agreements using IGMP agreements and IPv6 multicast domains, the connection equipment connects
When receiving the control stream packet of IPv4 multicast domains, the control stream packet for generating corresponding IPv6 multicast domains is sent to IPv6 multicasts
Domain, including：
When the control stream packet of IPv4 multicast domains is IGMPv1 or IGMPv2 relationship messages, connection equipment notifies the master of itself
Generator terminal mouth generates MLDv1 relationship messages, is sent to IPv6 multicast domains；Alternatively,
When the control stream packet of IPv4 multicast domains is that IGMPv3 relationships message and the host port use MLDv1 agreements,
Connection equipment notifies the host port to generate MLDv1 relationship messages, is sent to IPv6 multicast domains；Alternatively,
When the control stream packet of IPv4 multicast domains is that IGMPv3 relationships message and the host port use MLDv2 agreements,
Connection equipment notifies the host port to generate MLDv2 relationship messages, is sent to IPv6 multicast domains.
When IPv4 multicast domains use MLD agreements using IGMP agreements and IPv6 multicast domains, the connection equipment receives
When the control stream packet of IPv6 multicast domains, the control stream packet for generating corresponding IPv4 multicast domains is sent to IPv4 multicast domains, packet
It includes：
The control stream packet of IPv6 multicast domains uses IGMPv1 for the host port of MLDv1 relationships message and connection equipment
When agreement, connect equipment notifies the host port to generate IGMPv1 relationship messages, is sent to IPv4 multicast domains；Alternatively,
The control stream packet of IPv6 multicast domains be MLDv1 relationships message and the host port using IGMPv2 or
When IGMPv3 agreements, connection equipment notifies the host port to generate IGMPv2 relationship messages, is sent to IPv4 multicast domains；Or
Person,
When the control stream packet of IPv6 multicast domains is that MLDv2 relationships message and the host port use IGMPv1 agreements,
Connection equipment notifies the host port to generate IGMPv1 relationship messages, is sent to IPv4 multicast domains；Alternatively,
When the control stream packet of IPv6 multicast domains is that MLDv2 relationships message and the host port use IGMPv2 agreements,
Connection equipment notifies the host port to generate IGMPv2 relationship messages, is sent to IPv4 multicast domains；Alternatively,
When the control stream packet of IPv6 multicast domains is that MLDv2 relationships message and the host port use IGMPv3 agreements,
Connection equipment notifies the host port to generate IGMPv3 relationship messages, is sent to IPv4 multicast domains.
Before the control stream packet for generating corresponding IPv6 multicast domains, this method further includes：The connection equipment will
IPv4 address of cache in the control stream packet of the IPv4 multicast domains of reception is to the corresponding addresses IPv6；
Before the control stream packet for generating corresponding IPv4 multicast domains, this method further includes：The connection equipment will
IPv6 address of cache in the control stream packet of the IPv6 multicast domains of reception is to the corresponding addresses IPv4.
The IGMPv1 relationships message joins message for IGMPv1；
The IGMPv2 relationships message is that IGMPv2 joins message or IGMPv2 leaves message；
The IGMPv3 relationships message is that IGMPv3 joins message or IGMPv3 leaves message；
The MLDv1 relationships message is that MLDv1 joins message or MLDv1 leaves message；
The MLDv2 relationships message is that MLDv2 joins message or MLDv2 leaves message.
When IPv4 multicast domains use PIMv6 agreements using PIMv4 agreements and IPv6 multicast domains,
Equipment is connected by the value of the relevant field in the control stream packet of the IPv4 multicast domains of reception, by the corresponding values of IPv4
The corresponding values of IPv6 are converted to, the control stream packet of corresponding IPv6 multicast domains is generated；
Equipment is connected by the value of the relevant field in the control stream packet of the IPv6 multicast domains of reception, by the corresponding values of IPv6
The corresponding values of IPv4 are converted to, the control stream packet of corresponding IPv4 multicast domains is generated.
It is described when the control stream packet of the IPv4 multicast domains or the control stream packet of IPv6 multicast domains are hello packet
Relevant field includes：Addr Family fields, Secondary Address fields and checksum fields；
When the control stream packet of the IPv4 multicast domains or the control stream packet of IPv6 multicast domains are Register messages, institute
Stating relevant field includes：Multicast data packet fields and checksum fields；
The IPv4 multicast domains control stream packet or IPv6 multicast domains control stream packet be Register-not messages,
When Join messages, Prune messages or Assert messages, the relevant field includes：Addr Family fields, Mask Len words
Section, Group multicast Address fields, Source Address fields and checksum fields.
When IPv4 multicast domains use PIMv6 agreements using IGMP agreements and IPv6 multicast domains, the connection equipment receives
When the control stream packet of IPv4 multicast domains, the control stream packet for generating corresponding IPv6 multicast domains is sent to IPv6 multicast domains, packet
It includes：
When the control stream packet of IPv4 multicast domains is IGMP member relation messages, equipment is connected by the IGMP member relations
After IPv4 address of cache to the corresponding addresses IPv6 in message, notify the port of itself connection IPv6 multicast domain according to
The addresses IPv6 generate corresponding PIMv6 relationships message, are sent to IPv6 multicast domains；
The IGMP member relations message is that IGMP member joins message or IGMP member leaves message；
The PIMv6 relationships message is that PIMv6 joins message or PIMv6 leaves message.
When IPv4 multicast domains use MID agreements using PIMv4 agreements and IPv6 multicast domains, the connection equipment receives
When the control stream packet of IPv6 multicast domains, the control stream packet for generating corresponding IPv4 multicast domains is sent to IPv4 multicast domains, packet
It includes：
When the control stream packet of IPv6 multicast domains is MLD member relation messages, equipment is connected by the MLD member relations report
After IPv6 address of cache to the corresponding addresses IPv4 in text, notify the port of itself connection IPv4 multicast domain according to the IPv4
Address generates corresponding PIMv4 relationships message, is sent to IPv4 multicast domains；
The MLD member relations message is that MLD member joins message or MLD member leaves message；
The PIMv4 relationships message is that PIMv4 joins message or PIMv4 leaves message.
The present invention also provides the systems that multicast between a kind of IPv4 and IPv6 controls stream information intercommunication, including：It route end
Mouth, analysis module and host port, wherein：
When the routed port receives the control stream packet of IPv4 multicast domains, the analysis module notifies the host side
The control stream packet that mouth generates corresponding IPv6 multicast domains is sent to IPv6 multicast domains；
When the routed port receives the control stream packet of IPv6 multicast domains, the analysis module notifies the host side
The control stream packet that mouth generates corresponding IPv4 multicast domains is sent to IPv4 multicast domains.
The method and system of multicast control stream information intercommunication between IPv4 and IPv6 proposed by the present invention, according to IPv4 multicasts
The agreement that domain and IPv6 multicast domains use, by connecting equipment by the conversion between controlling stream packet progress IPv4 and IPv6, in fact
Existing multicast controls stream information intercommunication, to complete the foundation of multicast distributed tree in the environment of IPv4 and IPv6 coexist, can solve
Certainly in the migration course of IPv4 to IPv6, since the address family of multicast source, multicast recipient and transmission network operation mismatches
Caused multicast is difficult to the problem of carrying out.
Description of the drawings
Fig. 1 is that IPv4 multicast receivers are connected to MLD requestors by connecting equipment；
Fig. 2 is that be IPv6 multicast receivers be connected to igmp querying device by connecting equipment；
Fig. 3 is address of cache process；
Fig. 4 is the IPv4 multicast receivers access MLD requestors for running IGMPv1 agreements；
Fig. 5 is the IPv4 multicast receivers access MLD requestors for running IGMPv2 agreements；
Fig. 6 is the IPv4 multicast receivers MLD requestors for running IGMPv3 agreements；
Fig. 7 is the IPv6 multicast receivers igmp querying devices for running MLDv1 agreements；
Fig. 8 is the IPv6 multicast receivers igmp querying devices for running MLDv2 agreements；
Fig. 9 is the connection in the domains PIMv4 and the domains PIMv6；
Figure 10 is that IPv6 multicast receivers access the domains PIMv4；
Figure 11 is that IPv4 multicast receivers access the domains PIMv6.
Specific implementation mode
The main thought of multicast Interworking Scheme is between IPv4 and IPv6 of the present invention：
101, when connection equipment receives the control stream packet of IPv4 multicast domains, generate the control of corresponding IPv6 multicast domains
Stream packet is sent to IPv6 multicast domains；
102, when connection equipment receives the control stream packet of IPv6 multicast domains, generate the control of corresponding IPv4 multicast domains
Stream packet is sent to IPv4 multicast domains.
Wherein, multicast is carried out by connecting equipment when IPv4 multicast domains and IPv6 multicast domains control stream information intercommunication, to
Complete when the establishing of multicast distributed tree in the environment of IPv4 and IPv6 coexist, including following several processing scenes：IGMP- ＞
MLD, MLD- ＞ IGMP, PIMv4 ＜-＞ PIMv6, MLD- ＞ PIMv4 and IGMP- ＞ PIMv6.Wherein, IGMP, PIMv4 belong to
Agreement used in IPv4 multicast domains, MLD, PIMv6 belong to agreement used in IPv6 multicast domains.
The solution of the present invention under above-mentioned several scenes is described in detail below.
1, IGMP- ＞ MLD.
As shown in Figure 1, the IPv4 multicast receivers for running IGMP agreements in IPv4 multicast domains are connected to by connecting equipment
MLD requestors in IPv6 multicast domains.Then, it when connection equipment receives the control stream packet of IPv4 multicast domains, generates corresponding
The control stream packet of IPv6 multicast domains is sent to IPv6 multicast domains, specifically includes following several situations：
When the control stream packet of IPv4 multicast domains is IGMPv1 or IGMPv2 relationship messages, connection equipment notifies the master of itself
Generator terminal mouth generates MLDv1 relationship messages；Alternatively,
When the control stream packet of IPv4 multicast domains is that IGMPv3 relationships message and host port use MLDv1 agreements, connection
Equipment notifies host port to generate MLDv1 relationship messages；Alternatively,
When the control stream packet of IPv4 multicast domains is that IGMPv3 relationships message and host port use MLDv2 agreements, connection
Equipment notifies host port to generate MLDv2 relationship messages；
The control stream packet of generation is sent to the MLD requestors of IPv6 multicast domains.
2, MLD- ＞ IGMP.
As shown in Fig. 2, the IPv6 multicast receivers for running MLD agreements in IPv6 multicast domains are connected to by connecting equipment
Igmp querying device in IPv4 multicast domains.Then, it when connection equipment receives the control stream packet of IPv6 multicast domains, generates corresponding
The control stream packet of IPv4 multicast domains is sent to IPv4 multicast domains, specifically includes following several situations：
When the control stream packet of IPv6 multicast domains is that MLDv1 relationships message and host port use IGMPv1 agreements, connection
The notice host port of equipment generates IGMPv1 relationship messages；Alternatively,
The control stream packet of IPv6 multicast domains is MLDv1 relationships message and host port is assisted using IGMPv2 or IGMPv3
When view, connection equipment notice host port generates IGMPv2 relationship messages；Alternatively,
When the control stream packet of IPv6 multicast domains is that MLDv2 relationships message and host port use IGMPv1 agreements, connection
Equipment notifies host port to generate IGMPv1 relationship messages；Alternatively,
When the control stream packet of IPv6 multicast domains is that MLDv2 relationships message and host port use IGMPv2 agreements, connection
Equipment notifies the host port to generate IGMPv2 relationship messages；Alternatively,
When the control stream packet of IPv6 multicast domains is that MLDv2 relationships message and host port use IGMPv3 agreements, connection
Equipment notifies host port to generate IGMPv3 relationship messages；
The control stream packet of generation is sent to the igmp querying device of IPv4 multicast domains.
Above-mentioned IGMPv1 relationships message joins message for IGMPv1；
IGMPv2 relationship messages are that IGMPv2 joins message or IGMPv2 leaves message；
IGMPv3 relationship messages are that IGMPv3 joins message or IGMPv3 leaves message；
MLDv1 relationship messages are that MLDv1 joins message or MLDv1 leaves message；
MLDv2 relationship messages are that MLDv2 joins message or MLDv2 leaves message.
3, PIMv4 ＜-＞ PIMv6.
Equipment is connected by the value of the relevant field in the control stream packet of the IPv4 multicast domains of reception, by the corresponding values of IPv4
The corresponding values of IPv6 are converted to, the control stream packet of corresponding IPv6 multicast domains is generated；
Equipment is connected by the value of the relevant field in the control stream packet of the IPv6 multicast domains of reception, by the corresponding values of IPv6
The corresponding values of IPv4 are converted to, the control stream packet of corresponding IPv4 multicast domains is generated.
Wherein, it is above-mentioned when the control stream packet of IPv4 multicast domains or the control stream packet of IPv6 multicast domains are hello packet
Relevant field include：Addr Family fields, Secondary Address fields and checksum fields；
When the control stream packet of IPv4 multicast domains or the control stream packet of IPv6 multicast domains are Register messages, above-mentioned phase
Closing field includes：Multicast data packet fields, checksum fields；
The control stream packet of IPv4 multicast domains or the control stream packet of IPv6 multicast domains are Register-not messages, Join
When message, Prune messages or Assert messages, above-mentioned relevant field includes：Addr Family fields, Mask Len fields,
Group multicast Address fields, Source Address fields and checksum fields.
4, IGMP- ＞ PIMv6.
When connection equipment receives the control stream packet of IPv4 multicast domains, the control stream report of corresponding IPv6 multicast domains is generated
Text is sent to IPv6 multicast domains, specifically includes：The control stream packet for the IPv4 multicast domains that connection equipment receives is IGMP member
When relationship message, after the IPv4 address of cache in IGMP member relation messages to the corresponding addresses IPv6, notify that itself is connected
The port of IPv6 multicast domains generates corresponding PIMv6 relationships message according to the addresses IPv6, is sent to IPv6 multicast domains.
Wherein, IGMP member relations message is that IGMP member joins message or IGMP member leaves message；
PIMv6 relationship messages are that PIMv6 joins message or PIMv6 leaves message.
5, MLD- ＞ PIMv4.
When connection equipment receives the control stream packet of IPv6 multicast domains, the control stream report of corresponding IPv4 multicast domains is generated
Text is sent to IPv4 multicast domains, specifically includes：The control stream packet for the IPv6 multicast domains that connection equipment receives closes for MLD member
When being message, after the IPv6 address of cache in MLD member relation messages to the corresponding addresses IPv4, notify that itself connects IPv4
The port of multicast domain generates corresponding PIMv4 relationships message according to the addresses IPv4, is sent to IPv4 multicast domains.
MLD member relation messages are that MLD member joins message or MLD member leaves message；
PIMv4 relationship messages are that PIMv4 joins message or PIMv4 leaves message.
Technical scheme of the present invention is described in detail below by embodiment.
Mapping between embodiment one, the addresses IPv4 and the addresses IPv6.
Connect device configuration prefix after, can according to corresponding mapping algorithm by IPv4 address of cache to corresponding IPv6
Location, certainly, the process are reversible, such as shown in Fig. 3：
According to multicast prefix ff00:abc::/ 96, it can be by IPv4 multicast address 230.1.2.3 with being mapped to IPv6 multicasts
Location ff00:abc::230.1.2.3；Conversely, according to multicast prefix ff00:abc::/ 96, it can also be by IPv6 multicast address
ff00:abc::230.1.2.3 it is mapped to IPv4 multicast address 230.1.2.3；
According to unicast prefix 2001:db8::/ 96, it can be by IPv4 unicast address 192.1.2.3 with being mapped to IPv6 unicasts
Location 2001:db8::192.1.2.3；Conversely, according to unicast prefix 2001:db8::/ 96, it can also be by IPv6 unicast address
2001:db8::192.1.2.3 it is mapped to IPv4 unicast address 192.1.2.3.
The address arrived involved in subsequent embodiment is by taking embodiment one as an example.
Embodiment two, IGMP- ＞ MLD scenes.
Assuming that it is G (230.1.2.3) that IPv4 multicast receivers, which need the multicast group for being added or leaving, device configuration is connected
Multicast prefix is (ff00:abc::/96).
In conjunction with Fig. 4, when the IPv4 multicast receivers for running IGMPv1 agreements are connected to MLD requestors：
1, the IPv4 multicast receivers of operation IGMPv1 agreements send IGMPv1 and join message (i.e. report messages) to company
Equipment is connect, indicates that the multicast group G (230.1.2.3) that needs are added, G=230.1.2.3 are IPv4 multicast address；
2, connection equipment receives after IGMPv1 joins message, according to RFC4605 agreements, if the ends message triggering HOST
The forwarding state proportional table of mouth changes (addition forwarding state proportional table) and the multicast group G of request is deposited in IPv6 multicast domains
In available multicast services, then IPv4 multicast address G (230.1.2.3) is mapped to IPv6 multicast address G ' by connection equipment
(ff00:abc::230.1.2.3)；
3, the ports connection equipment notice HOST generate corresponding MLDv1 and join message, and IPv6 multicast address G ' is inserted
After the message, it is sent on MLD requestors.
In conjunction with Fig. 5, when the IPv4 multicast receivers for running IGMPv2 agreements are connected to MLD requestors：
1, operation IGMPv2 agreements IPv4 multicast receivers send IGMPv2 join message or IGMPv2 leave message to
Equipment is connected, indicates that the multicast group G (230.1.2.3) for needing to be added or leave, G=230.1.2.3 are IPv4 multicast address；
2, connection equipment receives IGMPv2 and joins message or after IGMPv2 leaves message, according to RFC4605 agreements, if
The forwarding state proportional tables of message triggering HOST ports changes (add or delete forwarding state proportional table) and asks
There are available multicast services in IPv6 multicast domains by multicast group G, then connecting equipment by IPv4 multicast address G (230.1.2.3)
It is mapped to IPv6 multicast address G ' (ff00:abc::230.1.2.3)；
3, the corresponding MLDv1 of connection equipment notice HOST port generations joins message or MLDv1 leaves message (with reception
Join message or leave message correspondence), and after IPv6 multicast address G ' is inserted the message, be sent on MLD requestors.
In conjunction with Fig. 6, when the IPv4 multicast receivers for running IGMPv3 agreements are connected to MLD requestors：
1, operation IGMPv3 agreements IPv4 multicast receivers send IGMPv3 join message or IGMPv3 leave message to
Equipment is connected, indicates the multicast group G (230.1.2.3) and corresponding multicast source S (192.1.2.3), G for needing to be added or leave
=230.1.2.3 is IPv4 multicast address, and S=192.1.2.3 is IPv4 unicast address；
2, connection equipment receives IGMPv3 and joins message or after IGMPv3 leaves message, according to RFC4605 agreements, if
The forwarding state proportional tables of message triggering HOST ports changes (add or delete forwarding state proportional table) and asks
There are available multicast services in IPv6 multicast domains by multicast group G, then connecting equipment by IPv4 multicast address G (230.1.2.3)
It is mapped to IPv6 multicast address G ' (ff00:abc::230.1.2.3), IPv4 unicast address S (192.1.2.3) is mapped to
IPv6 unicast address S ' (2001:db8::192.1.2.3)；
If 3, the ports HOST run MLDv2 agreements, connects the ports equipment notice HOST and generate corresponding MLDv2 additions
Message or MLDv2 leave message (with reception join message or to leave message corresponding), and it is IPv6 multicast address G and IPv6 is mono-
It broadcasts after address S ' inserts the message, and is sent to MLD requestors；
If the ports HOST run MLDv1 agreements, connects the ports equipment notice HOST and generate corresponding MLDv1 additions report
Text or MLDv1 leave message (with reception join message or to leave message corresponding), and by IPv6 multicast address G and IPv6 unicasts
After address S ' inserts the message, and it is sent to MLD requestors.
Embodiment three, MLD- ＞ IGMP scenes.
Assuming that it is G ' (ff00 that IPv6 multicast receivers, which need the multicast group for being added or leaving,:abc::230.1.2.3), even
It is (ff00 to connect the preconfigured multicast prefix of equipment:abc::/96).
In conjunction with Fig. 7, when the IPv6 multicast receivers for running MLDv1 agreements are connected to igmp querying device：
1, the IPv6 multicast receivers transmission MLDv1 of operation MLDv1 agreements joins message or MLDv1 leaves message to connection
Equipment indicates multicast group the G ' (ff00 that be added or leave:abc::230.1.2.3), G '=ff00:abc::230.1.2.3
For IPv6 multicast address；
2, connection equipment receives MLDv1 and joins message or after MLDv1 leaves message, according to RFC4605 agreements, if should
The group that the forwarding state proportional table of the ports message triggering HOST changes (add or delete forwarding state proportional table) and asks
Broadcasting group G ', there are available multicast services in IPv4 multicast domains, then connecting equipment by IPv6 multicast address G ' (ff00:abc::
230.1.2.3) it is mapped to IPv4 multicast address G (230.1.2.3)；
If 3, the ports HOST run IGMPv1 agreements, join message for MLDv1, the ports connection equipment notice HOST
Generate corresponding IGMPv1 to join message, and after IPv4 multicast address G is inserted the message, and be sent to igmp querying device (by
It only supports to join message in IGMPv1 agreements, does not support to leave message, therefore connection equipment ignores the MLDv1 received and leaves report
Text)；
If the ports HOST run IGMPv2 agreements, connects the ports equipment notice HOST and generate corresponding IGMPv2 additions
Message or IGMPv2 leave message (with reception join message or to leave message corresponding), and should by IPv4 multicast address G filling
After message, and it is sent to igmp querying device；
If the ports HOST run IGMPv3 agreements, connects the ports equipment notice HOST and generate corresponding IGMPv3 additions
Message or IGMPv3 leave message (with reception join message or to leave message corresponding), and should by IPv4 multicast address G filling
(at this point, the source address that IGMPv3 joins message or IGMPv3 leaves in message is defaulted as accepting or rejecting all multicasts after message
Source), it is sent to igmp querying device.
In conjunction with Fig. 8, when the IPv6 multicast receivers for running MLDv2 agreements are connected to igmp querying device：
1, the IPv6 multicast receivers transmission MLDv2 of operation MLDv2 agreements joins message or MLDv2 leaves message to connection
Equipment indicates multicast group the G ' (ff00 to be added or be left:abc::230.1.2.3) and multicast source S ' (2001:db8::
192.1.2.3), G '=ff00:abc::230.1.2.3 it is IPv6 multicast address, S '=2001:db8::192.1.2.3 being
IPv6 unicast address；
2, connection equipment receives MLDv2 and joins message or after MLDv2 leaves message, according to RFC4605 agreements, if should
The group that the forwarding state proportional table of the ports message triggering HOST changes (add or delete forwarding state proportional table) and asks
Broadcasting group G ', there are available multicast services in IPv4 multicast domains, then connecting equipment by IPv6 multicast address G ' (ff00:abc::
230.1.2.3 it) is mapped to IPv4 multicast address G (230.1.2.3), by IPv6 unicast address S ' (2001:db8::
192.1.2.3) it is mapped to IPv4 unicast address S (192.1.2.3)；
If 3, the ports HOST run IGMPv1 agreements, join message for MLDv2, the ports connection equipment notice HOST
Generate corresponding IGMPv1 to join message, and after IPv4 multicast address G is inserted the message, and be sent to igmp querying device (by
It only supports to join message in IGMPv1 agreements, does not support to leave message, therefore connection equipment ignores the MLDv2 received and leaves report
Text)；
If the ports HOST run IGMPv2 agreements, connects the ports equipment notice HOST and generate corresponding IGMPv2 additions
Message or IGMPv2 leave message (with reception join message or to leave message corresponding), and should by IPv4 multicast address G filling
After message, and it is sent to igmp querying device；
If the ports HOST run IGMPv3 agreements, connects the ports equipment notice HOST and generate corresponding IGMPv3 additions
Message or IGMPv3 leave message (with reception join message or to leave message corresponding), IPv4 multicast address G is inserted into the report
In text (IGMPv3 joins message or IGMPv3 leaves the source address of message and is set as S), and it is sent to igmp querying device.
Example IV, PIMv4 ＜-＞ PIMv6 scenes, if shown in Fig. 9：Wherein, the function of connecting equipment can be by PIM
Router realization,
1, PIM routers receive PIMv4Hello messages, if contained by the Secondary Address fields in the message
IPv4 unicast address be 10.1.2.3, then PIM routers generate corresponding PIMv6Hello messages, including：
Addr Family field values are set as 2, indicate IPv6 address families；
IPv4 unicast address 10.1.2.3 is mapped as IPv6 unicast address 2001:db8::10.1.2.3 after, filling
Secondary Address fields；
Reset the value of checksum；
Then, the PIMv6 hello packet of generation is sent to the domains PIMv6 by PIM routers.
If PIM routers receive PIMv6 hello packet, carries out opposite operation and obtains PIMv4Hello messages,
Then the domains PIMv4 are sent to.
2, PIM routers receive PIMv4 Register messages,
PIM routers generate corresponding PIMv6 Register messages, including：
IPv4 raw data packets in multicast data packet fields are converted into IPv6 data packets；
Reset the value of checksum；
Then, the PIMv6 Register messages of generation are sent to the domains PIMv6 by PIM routers.
If PIM routers receive PIMv6 Register messages, carries out opposite operation and obtain PIMv4Register
Message is subsequently sent to the domains PIMv4.
3, PIM routers receive PIMv4 Register-not messages, if in the message including IPv4 multicast address G
(230.1.2.3) and IPv4 unicast address S (10.1.2.3), then PIM routers generate corresponding PIMv6 Register-
When not messages, including：
Addr Family fields are set to 2, indicate IPv6 address families；
Mask Len fields are set to 128；
IPv4 multicast address 230.1.2.3 is mapped as IPv6 multicast address ff00:abc::After 230.1.2.3, filling
Group multicast Address fields；
IPv4 unicast address 10.1.2.3 is mapped as IPv6 unicast address 2001:db8::10.1.2.3 after, filling
Source Address fields；
Reset the value of checksum；
The PIMv6 Register-not messages of generation are sent to the domains PIMv6 by PIM routers.
If receiving PIMv6 Register-not messages, carries out opposite operation and obtain PIMv4Register-not
Message is subsequently sent to the domains PIMv4.
4, PIM routers receive PIMv4Join/Prune messages, if in the message including IPv4 multicast address G
(230.1.2.3) and IPv4 unicast address S (10.1.2.3), then PIM routers generate corresponding PIMv6 Join/Prune
Message, including：
Addr Family fields are set to 2, indicate IPv6 address families；
Mask Len fields are set to 128；
IPv4 multicast address 230.1.2.3 is mapped as IPv6 multicast address ff00:abc::After 230.1.2.3, filling
Group multicast Address fields；
IPv4 unicast address 10.1.2.3 is mapped as IPv6 unicast address 2001:db8::10.1.2.3 after, filling
Source Address fields；
Reset the value of checksum；
The PIMv6 Join/Prune messages of generation are sent to the domains PIMv6 by PIM routers.
If receiving PIMv6 Join/Prune messages, carries out opposite operation and obtain PIMv4 Join/Prune reports
Then text is sent to the domains PIMv4.
5, PIM routers receive PIMv4 Assert messages, if in the message including IPv4 multicast address G
(230.1.2.3) and IPv4 unicast address S (10.1.2.3), then PIM routers generate corresponding PIMv6Assert messages,
Including：
Addr Family fields are set to 2, indicate IPv6 address families；
Mask Len fields are set to 128；
IPv4 multicast address 230.1.2.3 is mapped as IPv6 multicast address ff00:abc::After 230.1.2.3, filling
Group multicast Address fields；
IPv4 unicast address 10.1.2.3 is mapped as IPv6 unicast address 2001:db8::10.1.2.3 after, filling
Source Address fields；
Reset the value of checksum；
The PIMv6 Assert messages of generation are sent to the domains PIMv6 by PIM routers.
If receiving PIMv6 Assert messages, carries out opposite operation and obtain PIMv4 Assert messages, then send out
Toward the domains PIMv4.
Embodiment five, MLD- ＞ PIMv4 scenes.
Assuming that it is G ' (ff00 that IPv6 multicast receivers, which need the multicast group for being added or leaving,:abc::230.1.2.3), group
It is S ' (2001 to broadcast source:db8::192.1.2.3), the multicast prefix of configuration is (ff00:abc::/ 96), as shown in Figure 10：
1, when MLD requestors receive the MLD member relations message that IPv6 multicast receivers are sent, (MLD member joins message
Or MLD member leaves message), multicast group the G ' (ff00 that display IPv6 multicast receivers will be added or leave:abc::
230.1.2.3), if MLD member relation messages use MLDv2 agreements, which can also show corresponding group
Broadcast source S ' (2001:db8::192.1.2.3)；
2, according to RFC4605 agreements, if MLD member relation messages make the forwarding state proportional table of MLD requestors send out
Changing (add or delete forwarding state proportional table) and request multicast group G ' exist in IPv4 multicast domains (i.e. the domains PIMv4)
Available multicast services, then MLD requestors are by IPv6 multicast address G ' (ff00:abc::230.1.2.3 IPv4 groups) are mapped to
Address G (230.1.2.3) is broadcast, if it does, can also be by IPv6 unicast address S ' (2001:db8::192.1.2.3 it) is mapped to
IPv4 unicast address S (192.1.2.3)；
3, MLD requestors generate corresponding PIMv4 relationships message (PIMv4 joins message or PIMv4 leaves message), and will
After IPv4 multicast address G (230.1.2.3) inserts the message with IPv4 unicast address S (if present)s, it is sent to the domains PIMv4
In.
Embodiment six, IGMP- ＞ PIMv6 scenes.
Assuming that it is G (230.1.2.3), multicast source S that IPv4 multicast receivers, which need the multicast group for being added or leaving,
The multicast prefix of (192.1.2.3), configuration are (ff00:abc::/ 96), as shown in figure 11：
1, when igmp querying device receives IGMP member relations message (IGMP member's addition report of IPv4 multicast receivers transmission
Text or IGMP member leave message, particularly, if it is IGMPv1 agreements, then join message for IGMP member), show IPv4 groups
The multicast group G (230.1.2.3) that recipient will be added or leave is broadcast, if IGMP member relation messages use IGMPv3 to assist
View, then can also show out corresponding multicast source S (192.1.2.3) in the message；
2, according to RFC4605 agreements, if IGMP member relation messages make the forwarding state proportional table of igmp querying device
It changes (add or delete forwarding state proportional table) and the multicast group G asked exists in IPv6 multicast domains (i.e. the domains PIMv6)
Available multicast services, then igmp querying device is mapped to IPv6 multicast address G ' (ff00 by igmp querying device:abc::
230.1.2.3), if it does, can also IPv6 unicast address S ' be mapped to IPv4 unicast address S (192.1.2.3)
(2001:db8::192.1.2.3)；
3, igmp querying device generates corresponding PIMv6 relationships message (PIMv6 joins message or PIMv6 leaves message), and
By IPv6 multicast address G ' (ff00:abc::230.1.2.3) with IPv6 unicast address S ' (2001:db8::192.1.2.3) (such as
Fruit presence) insert the message after, be sent in the domains PIMv6.
In order to realize the above method, the present invention also provides a kind of systems of multicast intercommunication between IPv4 and IPv6, this is
System can be applied in above-mentioned connection equipment, MLD requestors, igmp querying device, PIM routers, including：Routed port, analysis
Module and host port, wherein：
When routed port receives the control stream packet of IPv4 multicast domains, it is corresponding that analysis module notifies that host port generates
The control stream packet of IPv6 multicast domains is sent to IPv6 multicast domains；
When routed port receives the control stream packet of IPv6 multicast domains, it is corresponding that analysis module notifies that host port generates
The control stream packet of IPv4 multicast domains is sent to IPv4 multicast domains.
Analysis module is additionally operable to the IPv4 address of cache in the control stream packet for the IPv4 multicast domains that will be received to corresponding
The addresses IPv6；By the IPv6 address of cache in the control stream packet of the IPv6 multicast domains of reception to the corresponding addresses IPv4.
The foregoing is only a preferred embodiment of the present invention, is not intended to limit the scope of the present invention.
Claims (5)
1. a kind of method of multicast control stream information intercommunication between IPv4 and IPv6, which is characterized in that including：
When connection equipment receives the control stream packet of IPv4 multicast domains, the control stream packet hair of corresponding IPv6 multicast domains is generated
It is sent to IPv6 multicast domains；
When connection equipment receives the control stream packet of IPv6 multicast domains, the control stream packet hair of corresponding IPv4 multicast domains is generated
It is sent to IPv4 multicast domains；
Wherein, when IPv4 multicast domains use PIMv6 agreements using PIMv4 agreements and IPv6 multicast domains,
Equipment is connected by the value of the relevant field in the control stream packet of the IPv4 multicast domains of reception, is converted by the corresponding values of IPv4
For the corresponding values of IPv6, the control stream packet of corresponding IPv6 multicast domains is generated；
Equipment is connected by the value of the relevant field in the control stream packet of the IPv6 multicast domains of reception, is converted by the corresponding values of IPv6
For the corresponding values of IPv4, the control stream packet of corresponding IPv4 multicast domains is generated；Alternatively,
When IPv4 multicast domains use PIMv6 agreements using IGMP agreements and IPv6 multicast domains, the connection equipment receives IPv4
When the control stream packet of multicast domain, the control stream packet for generating corresponding IPv6 multicast domains is sent to IPv6 multicast domains, including：
When the control stream packet of IPv4 multicast domains is IGMP member relation messages, equipment is connected by the IGMP member relations message
In IPv4 address of cache to the corresponding addresses IPv6 after, notify itself connection IPv6 multicast domains port according to the IPv6
Location generates corresponding PIMv6 relationships message, is sent to IPv6 multicast domains；
The IGMP member relations message is that IGMP member joins message or IGMP member leaves message；
The PIMv6 relationships message is that PIMv6 joins message or PIMv6 leaves message；Alternatively,
When IPv4 multicast domains use MLD agreements using PIMv4 agreements and IPv6 multicast domains, the connection equipment receives IPv6
When the control stream packet of multicast domain, the control stream packet for generating corresponding IPv4 multicast domains is sent to IPv4 multicast domains, including：
When the control stream packet of IPv6 multicast domains is MLD member relation messages, connection equipment will be in the MLD member relations message
IPv6 address of cache to the corresponding addresses IPv4 after, notify itself connection IPv4 multicast domains port according to the addresses IPv4
Corresponding PIMv4 relationships message is generated, IPv4 multicast domains are sent to；
The MLD member relations message is that MLD member joins message or MLD member leaves message；
The PIMv4 relationships message is that PIMv4 joins message or PIMv4 leaves message.
2. the method that multicast controls stream information intercommunication between IPv4 and IPv6 according to claim 1, which is characterized in that described
Before the control stream packet for generating corresponding IPv6 multicast domains, this method further includes：The connection equipment is by the IPv4 groups of reception
The IPv4 address of cache in the control stream packet in domain is broadcast to the corresponding addresses IPv6；
Before the control stream packet for generating corresponding IPv4 multicast domains, this method further includes：The connection equipment will receive
IPv6 multicast domains control stream packet in IPv6 address of cache to the corresponding addresses IPv4.
3. the method that multicast controls stream information intercommunication between IPv4 and IPv6 according to claim 1, which is characterized in that described
IGMPv1 relationship messages join message for IGMPv1；
The IGMPv2 relationships message is that IGMPv2 joins message or IGMPv2 leaves message；
The IGMPv3 relationships message is that IGMPv3 joins message or IGMPv3 leaves message；
The MLDv1 relationships message is that MLDv1 joins message or MLDv1 leaves message；
The MLDv2 relationships message is that MLDv2 joins message or MLDv2 leaves message.
4. the method that multicast controls stream information intercommunication between IPv4 and IPv6 according to claim 1, which is characterized in that
When the control stream packet of the IPv4 multicast domains or the control stream packet of IPv6 multicast domains are hello packet, the correlation
Field includes：Addr Family fields, Secondary Address fields and checksum fields；
When the control stream packet of the IPv4 multicast domains or the control stream packet of IPv6 multicast domains are Register messages, the phase
Closing field includes：Multicast data packet fields and checksum fields；
The control stream packet of the IPv4 multicast domains or the control stream packet of IPv6 multicast domains are Register-not messages, Join
When message, Prune messages or Assert messages, the relevant field includes：Addr Family fields, Mask Len fields,
Group multicast Address fields, Source Address fields and checksum fields.
5. the system of multicast control stream information intercommunication between a kind of IPv4 and IPv6, which is characterized in that including：Routed port divides
Module and host port are analysed, wherein：
When the routed port receives the control stream packet of IPv4 multicast domains, the analysis module notifies the host port to give birth to
It is sent to IPv6 multicast domains at the control stream packet of corresponding IPv6 multicast domains；
When the routed port receives the control stream packet of IPv6 multicast domains, the analysis module notifies the host port to give birth to
It is sent to IPv4 multicast domains at the control stream packet of corresponding IPv4 multicast domains；
Wherein, when IPv4 multicast domains use PIMv6 agreements using PIMv4 agreements and IPv6 multicast domains,
Equipment is connected by the value of the relevant field in the control stream packet of the IPv4 multicast domains of reception, is converted by the corresponding values of IPv4
For the corresponding values of IPv6, the control stream packet of corresponding IPv6 multicast domains is generated；
Equipment is connected by the value of the relevant field in the control stream packet of the IPv6 multicast domains of reception, is converted by the corresponding values of IPv6
For the corresponding values of IPv4, the control stream packet of corresponding IPv4 multicast domains is generated；Alternatively,
When IPv4 multicast domains use PIMv6 agreements using IGMP agreements and IPv6 multicast domains, the connection equipment receives IPv4
When the control stream packet of multicast domain, the control stream packet for generating corresponding IPv6 multicast domains is sent to IPv6 multicast domains, including：
When the control stream packet of IPv4 multicast domains is IGMP member relation messages, equipment is connected by the IGMP member relations message
In IPv4 address of cache to the corresponding addresses IPv6 after, notify itself connection IPv6 multicast domains port according to the IPv6
Location generates corresponding PIMv6 relationships message, is sent to IPv6 multicast domains；
The IGMP member relations message is that IGMP member joins message or IGMP member leaves message；
The PIMv6 relationships message is that PIMv6 joins message or PIMv6 leaves message；Alternatively,
When IPv4 multicast domains use MLD agreements using PIMv4 agreements and IPv6 multicast domains, the connection equipment receives IPv6
When the control stream packet of multicast domain, the control stream packet for generating corresponding IPv4 multicast domains is sent to IPv4 multicast domains, including：
When the control stream packet of IPv6 multicast domains is MLD member relation messages, connection equipment will be in the MLD member relations message
IPv6 address of cache to the corresponding addresses IPv4 after, notify itself connection IPv4 multicast domains port according to the addresses IPv4
Corresponding PIMv4 relationships message is generated, IPv4 multicast domains are sent to；
The MLD member relations message is that MLD member joins message or MLD member leaves message；
The PIMv4 relationships message is that PIMv4 joins message or PIMv4 leaves message.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201110341730.4A CN103095585B (en) | 2011-11-02 | 2011-11-02 | The method and system of multicast control stream information intercommunication between a kind of IPv4 and IPv6 |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201110341730.4A CN103095585B (en) | 2011-11-02 | 2011-11-02 | The method and system of multicast control stream information intercommunication between a kind of IPv4 and IPv6 |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN103095585A CN103095585A (en) | 2013-05-08 |
| CN103095585B true CN103095585B (en) | 2018-08-07 |
Family
ID=48207738
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201110341730.4A Active CN103095585B (en) | 2011-11-02 | 2011-11-02 | The method and system of multicast control stream information intercommunication between a kind of IPv4 and IPv6 |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN103095585B (en) |
Families Citing this family (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN114915589A (en) * | 2021-02-10 | 2022-08-16 | 华为技术有限公司 | Message transmission method and device |
| US20230065679A1 (en) * | 2021-08-25 | 2023-03-02 | Cisco Technology, Inc. | Lightweight path maximum transmission unit for wireless multicast overlay |
Family Cites Families (7)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN1870569B (en) * | 2005-05-25 | 2012-02-08 | 国际商业机器公司 | Network system and its management method, communication terminal and file transmitting method |
| CN101114900A (en) * | 2006-07-27 | 2008-01-30 | 上海贝尔阿尔卡特股份有限公司 | Multicast service authentication method and device, system |
| CN101175068B (en) * | 2006-11-02 | 2011-08-17 | 上海未来宽带技术及应用工程研究中心有限公司 | Multi-version multicast protocol amalgamation method |
| CN101374069B (en) * | 2007-08-25 | 2011-07-06 | 华为技术有限公司 | Method, system and equipment for transforming multicast packet |
| CN101488873B (en) * | 2009-02-19 | 2011-01-05 | 杭州华三通信技术有限公司 | Multicast joining method and system |
| JP5340062B2 (en) * | 2009-07-14 | 2013-11-13 | アラクサラネットワークス株式会社 | Network relay device and network system |
| CN101989952B (en) * | 2010-11-03 | 2014-12-17 | 中兴通讯股份有限公司 | Multicasting method and device |
-
2011
- 2011-11-02 CN CN201110341730.4A patent/CN103095585B/en active Active
Also Published As
| Publication number | Publication date |
|---|---|
| CN103095585A (en) | 2013-05-08 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| US8054766B2 (en) | Method and tool for IP multicast network address translation (MNAT) | |
| US7894428B2 (en) | Packet relay device | |
| US8774038B2 (en) | Multicast support for dual stack-lite and internet protocol version six rapid deployment on internet protocol version four infrastructures | |
| US9426093B2 (en) | Multicast interworking systems and methods | |
| US9344382B2 (en) | Multicast support for internet protocol version four residual deployment via encapsulation or translation | |
| EP1432172A2 (en) | Method and device for multicast group management | |
| CN103095585B (en) | The method and system of multicast control stream information intercommunication between a kind of IPv4 and IPv6 | |
| US9641649B2 (en) | IGMP/MLD translation | |
| Braun et al. | Multicast for small conferences | |
| Hjálmtýsson et al. | Overcoming last-hop/first-hop problems in IP multicast | |
| CN102780567A (en) | Multicast service bearing method and system for DS-lite network architecture as well as network node | |
| Chmielewski et al. | Application of IP multicast in embedded systems with openWRT | |
| Boucadair et al. | Delivery of IPv4 Multicast Services to IPv4 Clients over an IPv6 Multicast Network | |
| Boucadair et al. | RFC 8114: Delivery of IPv4 Multicast Services to IPv4 Clients over an IPv6 Multicast Network | |
| Metz et al. | A look at native IPv6 multicast | |
| Li et al. | A home gateway based multicast transit solution and implementation on DS-Lite | |
| KR100747599B1 (en) | System and method for providing multicast routing using a multicast listener discovery proxy in home network | |
| Ghanwani et al. | A Framework for Multicast in Network Virtualization over Layer 3 | |
| Zhang | The study and implementation of IPv4-IPv6 multicast transition gateway | |
| Liu et al. | Metrino-an application-level multicast system for real-time video communication | |
| Aweya | IP Multicast Routing Protocols: Concepts and Designs | |
| Yun et al. | Multicast architecture for IPv6 over DVB-RCS satellite networks | |
| CN104022958B (en) | A kind of control method of multicast message | |
| Pike et al. | IPv6 and multicast filtering for high-performance multimedia applications | |
| KR20000027471A (en) | Method for transmitting session data of a multicast router |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| C06 | Publication | ||
| PB01 | Publication | ||
| C10 | Entry into substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| GR01 | Patent grant | ||
| GR01 | Patent grant |