I am studying the possibilities of using IPv6 potentialities to design a customized IPv6 data packet that has the following features:
1. Combines many fragments of different data in one packet.
For example, we have Data 1 (video), Data 2 (image), Data 3 (audio); F11 is the 1st fragment of Data 1, F21 (1st fragment of Data 2), F31 (1st fragment of Data 3), these fragments will be kept in Packet P1 (the 1st data packet). P1 should be as follow:
| IPv6 header | TCP header | TCP payload | + + + + | F11 | F21 | F31 |
2. Specifies all destinations' information (IP addresses, Ports, etc) of each fragment in packets (P1, P2, ..., Pn) so each data fragment is routed to its destination.
Data 1 (F11) --to--> Dest 1 -- Data 2 (F21) --to--> Dest 2 |--> The destinations may not be in the same network Data 3 (F31) --to--> Dest 3 --
Update: an illustrative image added to explain more. Here, we consider that the type of all Data is video (for the sake of simplicity)
I am thinking about IPv6 Jumbogram (RFC 2675) where
65,535 Bytes < the size of packet < 4 Gb , but the main challenges facing me currently, are:
- Is it possible to add more fields for destination addresses in the header ?
- Is it possible to put different data fragments F11, F21, F31 together in the TCP payload (of the Jumbogram), and more importantly, how can routers access/forward these fragments in the network ? ... Hop-By-Hop options header is used when there is a Jumbogram payload.
Since IPv6 basic header is fixed (40 Bytes), the IPv6 Extension headers seems to me relevant to do this customization, however, I need more orientations and advises for its feasibility.