DE102016001869A1 - Method for optimizing the routing of IPv6 traffic (IPway) - Google Patents

Abstract

IP networks are used in global data connections between information processing equipment. Today, IPv4 and IPv6 networks are used. The biggest difference between the two variants is that IPv6 allows significantly more than four billion subscribers to be addressed. Each participant has a network-wide unique address, its membership in subnets can be recognized at the address. IP networks work in a package-oriented way. It is divided into control information and user data. The division into certain areas is called a frame. Different tasks of the devices are separated by hierarchical levels (backup, mediation, transport, session). Control information and user data of a higher layer are packed in the payload of the lower layer. The frames are thus nested hierarchically. Today's methods try to be particularly easy to integrate into existing networks by an excess of compatibility and keep control information that have no meaning in modern networks. To separate networks into subareas and to enable different paths in networks routers are necessary. Routers have multiple ports that can be connected to different subnets. A router accepts a data packet at a port and decides to which port it passes it. These decisions take time and slow down the path of a data packet. The destination network or another router can be connected to this port. A passage through a device is called a hop. With the number of hops required, the duration of a packet is extended by a network. The number of redirects is displayed in a hop counter. The hop counter counts from the predicted number of required hops, one per device, down to zero. The present invention relates to methods for reducing the delay time when traversing a router. The following new method points are introduced: Edgerouter translate the packets of conventional networks into packets of the presented method. Routers inside the network are called corer routers, they can only forward the novel packets of the presented method. Decisions about forwarding should be made as early as possible, so the necessary information is placed in the stream at the beginning. The reorganization takes place with each hop so that it is optimal for the following router. In addition, the path of a packet is encoded by the network in the address. The address of a subscriber is unique only from one point of the network for a particular route through the network. Two subscribers can have the same relative address from different parts of the network. A subscriber can have two different relative addresses from one location of the network, if data packets take different paths in the network. The destination address in a packet changes from hop to hop as it traverses the network. The necessary procedure is called IPwoy. The method presented here will fully meet these requirements and thus enable a significant acceleration of Internet Protocol-based networks.

Description

Background / state of the art

In network segments where only IPv6 routing takes place, the path of a packet through the network is given based on the address information in the IPv6 header. This consists, as in shown, consisting of 64 bit header information and twice 128 bit address information. Defining an ideal router as a data flow machine or processor, which accomplishes the forwarding of a packet as soon as the destination information has been read, one recognizes the unfavorable structure of the Internet protocols IPv4 and IPv6. Both protocol versions are located as in and recognizable, between the beginning of the packet and the destination address, information that is not needed for the routing. This unnecessarily delays packet forwarding in the router. Examples of this IPv6-based routing are provided by Choi and others [1] and Foglar [3].

The method described here differs fundamentally from the approaches presented here: Goldman and others [4] present a virtualization of Layer 2 and Layer 3 information to optimize network traffic to virtual hosts. Chunduri and others [2] and Who among others [8] present methods for optimizing MAC-IPv6 mapping, Shimizu and others [6] considers the security aspect of this relation. Mulligan [5] presents a method for compressing the IPv6 header using Layer 2 information. However, this method is used here to save redundant bits in the header and not to gain faster access to information that is important for routing.

description

1 routing

shows an exemplary structure of an IPway network. At the edges of the network are the Edgerouter E1 and E2, the conversion between the IPv6 standard and IPway realize. Inside there are several corer routers with different numbers of ports. Depending on the number of ports, the routers can use different bit widths for numbering. Thus, one router can have 4 ports on the way, another can have 1024 ports. The method uses only the necessary bit width.

A relative address always contains the information relevant for the next hop in the first place. The routing of an IPway packet is based on the route information in the data field of the same name. As can be seen in Figure 3, the path field contains the routing information of the individual hops in the order in which they occur. In the event of a hop, the router removes the number of the port via which it must forward the packet and shifts the address by the appropriate number of bits to the left. Then he adds the number of the port from which he received the packet to the end of the address field. The bit width of the port number is known to the router because it knows the number of its ports. In this way, for each hop from the relative address for the way out step by step the address for the return.

In one example, information is meant to be through the network from Edgerouter (E1) to Edgerouter 2 (E2). The way is chosen, which leads through Corerouter 1, 3 and 6. Depending on the number of ports of the routers crossed, the information is coded by a different number of bits. The selected connection is described by the bit sequence 1 11 011 01. At the end of the transmission, as in the method described above, the address for the return path is known, it is 00 10 000 00. The length of the path field does not change within the network segment, since all ports of a router with the same number of Bits are coded. Only when receiving at the end node of the path can a length change occur when the ports of start and target device are coded with a different number of bits.

2 package construction

Figure 5 shows the structure of an IPway packet. Based on the IPv6 packet, a 256-bit path field was introduced at the beginning of the frame, this contains a 1-byte hop counter, which is explained in more detail in section 3. The existing IPv6 source and destination addresses are not needed on pure IPway networks and are only needed to tunnel IPv6 traffic over an IPway network segment.

3 corer routers

Corer routers are located inside the network and process only IPway packets. This begins by sending a packet as soon as the first x = ld (N) bits of the way field have been read. Since N is the number of ports of a router, each router knows the number of bits to be processed. All processed bits are discarded when forwarding the packet. The length of the path field is initially considered static and is 256 bits. If this shift is implemented by a shift register illustrated in FIG. 3, this does not delay the packet since the router immediately after the routing information is available to it begins to transmit the further path bits and only the identifier of the input port to the end of the path - Field attaches. By doing so, the information needed for the current hop is always at the beginning of the address block. By adding the input information, the path of the package remains traceable to address any answers. For each hop, the hop counter at the beginning of the IPway packet is decremented by x. If this counter reaches 0, the parcel arrived at its destination and does not need to be forwarded. For the return route, the hop counter must be reconstructed from a copy in the frame.

1

Start of frame delimiter

, eingelesen, daraufhin wird in Schritt 3 der Hop-Counter ausgelesen. Schritt 4 ist eine Entscheidung, wenn der Hop-Counter 0 ist, ist das Paket in Schritt 5 am Ziel angekommen und der Inhalt wird ggf. verarbeitet. Beträgt der Hop-Counter des Pakets nicht 0, werden in Schritt 6, n = ld(N) Bit des Wegfeldes gelesen. In Schritt 7 wird anhand der Wegbits der Ausgangsport ermittelt. Die Schicht 1 Information, also Präambel und SFD, wird in Schritt 8 versendet, in Schritt 9 werden die weiteren Weginformationen gelesen und gleichzeitig weiter gesendet. Schritt 10 beinhaltet das Senden der ID der Eingangsports. In Schritt 11 wird weiterhin über am Eingangsport gelesen und Pakete über den Ausgangsport verschickt, dieser Schritt wird solange wiederholt, bis Bedingung 12, eine Prüfung auf das Ende des Paketes, erfüllt ist. Ist das Paketende erreicht, ist die Verarbeitung beendet. (Schritt 13) 6 shows the steps of packet processing in a corerouter. This figure corresponds to Figure 7 which shows the same process from the perspective of the data packet. In step 1 has arrived a new package, which is to be processed. In step 2 Layer 1 information, such as preamble and SFD 1

1

Start of frame delimiter

, read in, then it will step in 3 the hop counter read out. step 4 is a decision, if the hop counter is 0, the package is in step 5 arrived at the destination and the content is processed if necessary. If the hop counter of the package is not 0, go to step 6 , n = ld (N) Bit of the way field read. In step 7 is determined based on the way bits of the output port. The layer 1 information, ie preamble and SFD, is in step 8th shipped, in step 9 the further route information is read and sent at the same time. step 10 involves sending the ID of the input ports. In step 11 is still read over at the input port and packets sent via the output port, this step is repeated until condition 12 , a check on the end of the package, is met. When the end of the packet is reached, processing is complete. (Step 13 )

Figure 7 shows the packet processing of an IPway packet within a corerouter. Looking only at OSI layer 3, the router must read 64 bits + 128 bits + 128 bits = 320 bits of the packet in a conventional IPv6 packet before the routing information is available to it. Assuming that a corerouter has a maximum of 1024 ports, IPway only needs to read 8 bits + ld (1024) bits = 18 bits. This results in a gain of 320 bits - 18 bits = 302 bits per corerouter. The time it took an IP router to determine the next hop from the address information was not quantized here. However, the immediate reading of the path from the path information contained in the packet is an essential part of the method and represents a significant advantage of the IPway router compared to IP routers.

4 Edgerouter

2

Beliebige Teilnehmer außerhalb des IPway-Netzes

zum ersten Mal miteinander, ermittelt der Corerouter mit Hilfe eines geeigneten Algorithmus3

3

Beispielsweise durch Flooding 171

den bevorzugten Weg durch das IPway-Netzwerksegment. Die Wegermittlung kann auch durch eine SDN-Schnittstelle am Router beeinflusst werden. Diesen Weg speichert er zusammen mit der Ziel-IPv6-Adresse zur späteren Verwendung in seiner Datenbank ab. Da der Weg durch das IPway-Netzwerk nicht mit den IP6-Source- und Destination-Adressen korreliert, müssen die IPv6-Adressinformationen innerhalb des IPway-Paketes übertragen werden. Wie in Bild 5 dargestellt werden diese Adressinformationen im IPway-Header übertragen. Tritt ein IPv6-Paket in ein IPway-Netz ein, so erfahren die Daten im Vergleich zur herkömmlichen Verarbeitung als IPv6 Paket eine Verzögerung von 8 Bit + 256 Bit = 264 Bit durch das Anfügen der Weginformation sowie des Hop-Counters, wie in Bild 8 ersichtlich.The Edgerouter, which are positioned at the borders of the IPway network segment, realize the conversion between IPv6 and IPway. If all network elements are IPway-enabled, no Edgerouter is needed. Communicate two endpoints 2

2

Any participants outside the IPway network

for the first time with each other, the corerouter determines with the help of a suitable algorithm 3

3

For example, by flooding 171

the preferred path through the IPway network segment. The route determination can also be influenced by an SDN interface on the router. It saves this route together with the destination IPv6 address for later use in its database. Since the path through the IPway network does not correlate with the IP6 source and destination addresses, the IPv6 address information must be transmitted within the IPway packet. As shown in Figure 5, this address information is transmitted in the IPway header. When an IPv6 packet enters an IPway network, the data experiences a delay of 8 bits + 256 bits = 264 bits compared to conventional processing as an IPv6 packet by adding the path information and the hop counter, as shown in Figure 8 seen.

9 shows the procedure for an incoming packet in an IPway Edgerouter v1. In step 21 arrive a new package from outside. For this will be in step 22 Layer 1 and Layer 2 read information. During step 23 If more bits are read, this step is repeated until in step 24 all target information of layer 3 has been read. Is this condition 24 is met, in step 25 Determines whether the route to the destination address already exists in the database. If the route is not saved, it will step in 26 the way to the output Edgerouter determined. In step 27 the first package is noted, at the same time in step 28 the path and the layer 3 destination addresses with a new ID stored in the database. The threads 27 and 28 end here in states 199 and 200 without a dependency on the rest of the plotline.

Is the path already stored in the database or has been step 26 redetermined and in step 28 stored in step 29 the output port of the route is read from the database. In step 30 More bits are read from the input port, at the same time in step 31 Layer 1 and layer 2 Information about the output port sent. step 32 involves sending the way field. Continue to be in step 33 the IPv6 destination address, in step 34 the IPv6 source address, in step 35 the IPv6 header and in step 36 sent a copy of the hop counter. Then done by step 37 and condition 38 a reading and sending the remaining data of the packet until the end of the packet is reached (condition 38 ). After sending the last bit, the process is with state 39 completed.

Figure 10 shows the exit of an IPway packet from the network segment. With the IPv6 packet, the routing information is available after 64 bits + 128 bits + 128 bits = 320 bits. An ordinary IPv6 router needs to read another 320 bits before it can use a complicated computation to determine the packet's path through the network. Both differences, the small number of bits to read and the omission of the routing computation lead to extreme speed advantages of the IPway method. The Edgerouter must have read the IPv6 destination address field within the IPway frame in order to forward the packet by reading 8 bits + 256 bits + 128 bits = 392 bits. The delay compared to processing a conventional IPv6 packet is thus 392 bits - 320 bits = 72 bits. The sum of the packet delay caused by IPway when entering and exiting the IPway network segment is thus 264 bits + 72 bits = 336 bits. Even if two IPway corer routers are used, the disadvantage of converting IPv6 to IPway and back is eliminated. Figure 9 and Figure 11 describe the process of packet processing in the IPway Edgerouter.

11 shows the procedure for outgoing packets. In step 41 is a new package available from within. For this will be in step 42 the layer 1 and layer 2 information read out. After that, in step 43 the hop counter is determined. Is this in step 44 not 0 (condition 44 ), starting from step 45 as shown in Figure 6. If the value of the counter is in step 44 0, in step 46 the way and in step 47 read the IPv6 addresses. In step 48 the output port is determined by the IPv6 address, this will be in step 49 Posted. At the same time in step 50 read the IPv6 header. Furthermore, in step 51 the IPv6 header and in step 52 sent the IPv6 addresses. In step 53 Further data is read from the input port and immediately sent via the output port. This process is repeated until the condition 54 applies and the end of the package is reached. The process will be in step 55 completed.

In the following, two optimizations of IPway are described which aim for a variable path length as well as a reduction of the overlay caused by the transmission of IPv6 addresses.

5 IPway.2

Depending on the number of hops within an IPway network, different numbers of bits are required to transmit this information. This optimization introduces a variable way field whose length is given by an 8-byte length field. Otherwise, the treatment of IPway packets works analogous to the previous procedure. 9 is also valid for the packet processing of the modified Edgerouter, describes the process for outgoing packets.

This optimization gives the way field a variable length of W, correspondingly changing the delays and time gains in packet processing within the Core and Edger routers.

Profit per Corerouter: 320 bits - (8 bits + 8 bits + ld (1024) bits) = 294 bits
Loss on Edgerouter in: 8 bits + 8 bits + W bits = 16 + W bits
Loss on Edgerouter out: 8 bits + 8 bits + W bits + 128 bits - 320 bits = W - 176 bits
Total gain on Edgerouters: - (W - 176 bits) - (16 + W bits) = 160 - 2 W bits

4

Mit 80 Bit ließen sich beispielsweise 8 Hops über Router mit einer Portanzahl von jeweils 1024 Ports kodieren.

.This optimization results in comparison to the transmission of Standard IPv6 packets a gain of time on the Edgeroutern as long as the length of the Wegfeldes a length of 160 bits / 2 = 80 bits does not exceed 4

4

With 80 bits, for example, 8 hops could be encoded via routers with a port number of 1024 ports each.

,

12 shows the process of packet processing for outgoing packets. In step 81 there is a new package from which in step 82 the layer 1 and layer 2 information and in the step 83 the hop counter is read. In step 84 if the hop counter is checked for 0, this is not the case, the further processing goes to step 85 as in 6 from. If the hop counter is 0, in step 86 the path-length field, in step 87 the way and in step 88 read the IPv6 addresses. Then in step 89 the output port is determined by the IPv6 address. In step 90 the layer 1 and layer 2 information are sent, at the same time in step 91 read the IPv6 header. Furthermore, in step 92 the IPv6 header and in step 93 sent the IPv6 address. In step 94 the remainder of the packet is read at the input port and sent simultaneously via the output port. This step is repeated until the condition 95 (End of parcel) is fulfilled and thus the parcel end has been reached. With step 96 the process is finished.

6 IPway.3

5

nachfolgend Hash genannt

der Länge 24 Bit und der IPway-Weginformation. Diese Optimierung führt zwei weitere IPway-Frame-Varianten ein, welche in den Bildern 18 und 19 dargestellt wurden. Wird eine Route durch das IPway-Netzwerk erstmalig genutzt speichert der erste Edgerouter die Information über den ermittelten Weg, das IPv6-Adressen-Paar, sowie einer laufenden Nummer in seiner Datenbank. Anschließend überträgt er das Datenpaket, wie in Bild 18 dargestellt, mit den IPv6-Adresse und der laufenden Nummer. Der Edgerouter am Netzausgang speichert ebenfalls die Information über das Wege-Feld, die laufende Nummer sowie die IPv6-Adressen. In weiteren Paketen dieses Kommunikationspfades ist somit die Information der IPv6-Adressen durch die laufende Nummer sowie das Wege-Feld kodiert und muss nicht zusätzlich übertragen werden. Die Unterscheidung ob ein Paket, das erst eines Streams ist erfolgt durch das setzen des Flag-Feldes im Paket. Der Übertragung erfolgt durch den Frame wie er in Bild 19 dargestellt ist.This optimization of the IPway protocol describes mapping the IPv6 addresses within the IPway network segment to a combination of an ID 5

5

hereafter called hash

24-bit length and IPway route information. This optimization introduces two additional IPway frame variants, which are shown in Figures 18 and 19. If a route through the IPway network is used for the first time, the first Edgerouter saves the information about the determined route, the IPv6 address pair, as well as a consecutive number in its database. It then transmits the data packet, as shown in Figure 18, with the IPv6 address and serial number. The Edgerouter at the network output also stores the information about the path field, the serial number and the IPv6 addresses. In further packets of this communication path, the information of the IPv6 addresses is thus coded by the consecutive number and the path field and does not have to be additionally transmitted. The distinction whether a packet that is only a stream is done by setting the flag field in the packet. The transmission takes place through the frame as shown in Figure 19.

14 and 15 show the process of packet processing of incoming packets. 14 sits down in 15 continued. In step 101 Arrives a new package from outside the Edgerouter. The layer 1 and layer 2 information will be in step 102 read. In step 103 and step 104 the layer 3 destination information is searched in the package. step 103 is repeated until the condition 104 applies and the layer 3 destination information has been read. In step 105 a decision is made as to whether the route to the destination address already exists in the database. If this is not the case, then step 107 and the way to the output Edgerouter, analogous to IPwayv2 determined. Thereupon will be in 108 created a note that this is the first package with this path. At the same time in step 109 the path and the layer 3 destination addresses are stored under a new ID in the database. The threads 108 and 109 end here in each case in the states 203 and 204 without a dependency on the rest of the plotline. After this step or if in step 106 already known the way to the destination address, the output port of the way in step 106 established. In step 110 Further bits are read from the input port and simultaneously in step 111 Layer 1 information, Preamble and SFD, sent via the output port. Continue to be in step 112 the length field of the path and in step 113 sent the way field. In step 114 ( ) checks if the package was the first package with this goal. If this is the case with step 115 , the sending of a flag, which includes the information "first packet" continued. Furthermore, in step 116 the IPv6 destination address, in step 117 the IPv6 source address, in step 118 the new ID and in step 119 sent the IPv6 header. If the package is not the first, it will be in step 120 signaled with a flag. In step 121 will be the appropriate ID to the IPv6 way tuple and in step 122 sent the IPv6 header. After both variants follows step 123 in which a copy of the hop counters is sent. Thereupon, in step 124 further data is read from the input port and sent immediately via the output port. This process is repeated until the condition in step 125 true and the end of the package has been sent. With step 126 the process is complete.

16 and 17 show the process of packet processing on outgoing packets. If an IPway packet reaches an inner port of an Edgerouter (state 131 ) are first in the steps 132 and 133 The layer 1 and layer 2 information as well as the IPway-Hop-Counter are read. In decision 134 Checks if the hop counter is 0. If the hop counter has a value greater than 0, it is analogous to the corerouter as in method. If the hop counter is 0, follow with step 136 reading the path length field as well as in step 137 reading the way. In step 138 the flag for the labeling of a new packet is read. The process now continues in Fig. 17. This transition is through the states 205 and 206 realized. With the decision 139 the currently read flag is evaluated. Depending on whether it is an unknown package, it will step 143 or step 140 continued. If the flag is not set and thus a record is stored in the router database in step 143 the ID of the record is read from the input port and in step 144 the IPv6 addresses belonging to the (ID, path) tuple are queried from the database. Is the package loud step 139 known, follow in step 140 reading the IPv6 addresses from the input port. Subsequently, in step 141 the ID of the package is read from the input port and in step 142 the triple (path, ID, IPv6 addresses) is stored in the database. Simultaneously with step 141 takes place in step 145 Determining the output port based on the now known IPv6 addresses. step 145 also follows step 144 , In the further process, the transmission of layer 1 and layer 2 is followed by information about the specified output port (step 146 ). At the same time, the IPv6 header is read from the input port (step 147 ). This is followed by sending the IPv6 header and the IPv6 addresses (steps 148 and 149 ). Subsequently, the remaining data is read from the input port and sent via the output port (step 150 ). This process is repeated until the end of the packet has been read (condition 151 ). The process ends after sending the last bit in the state 152 ,

If such an optimized IPway packet leaves the network segment, the Edgerouter now only has to read the 24-bit hash value to determine the IPv6 addresses for the reconstruction of the IPv6 packet. This optimization additionally reduces the time loss of an IPway packet.

Profit per Corerouter: 320 bits - (8 bits + 8 bits + ld (1024) bits) = 294 bits
Loss on Edgerouter in: 8 bits + 8 bits + W bits = 16 + W bits
Loss on Edgerouter out: 8 bits + 8 bits + W bits + 24 bits - 320 bits = W - 280 bits
Total gain on the Edgerouters: - (W - 280 bits) - (16 + W bits) = 264 - 2 W bits

This optimization saves Edgerouters time compared to standard IPv6 packets as long as the length of the path does not exceed 132 bits.

6.1 Summary

By combining the methods just presented in the edge and core routers, the following time savings can be achieved in comparison to the transmission of an IPv6 packet via the same number of network nodes:

Profit per Corerouter: 294 Bit
Total profit on Edgeroutern: 264 - 2 W bit
Where W can realistically be assumed to be 80 bits.

6.2 IPv4

6

Header-Quelladresse-Zieladresse-Daten

von IPv4- und IPv6-Paketen lassen sich die durch IPway vorgestellten Optimierungen auch auf IPv4-Pakete anwenden. Da IPway auf der Verlagerung von routingrelevanten Informationen an den Paketanfang basiert, lässt sich dieses Verfahren auch auf IPv4-Pakete anwenden.By the similar construction 6

6

Header source address destination address data

for IPv4 and IPv6 packets, the optimizations introduced by IPway can also be applied to IPv4 packets. Because IPway relies on relocating routing-related information to the beginning of the packet, this technique also applies to IPv4 packets.

List of Figures

• 1 (Prior Art) Abstracted IPv6 packet within a MAC 802.3 payload.
• 2 (Prior Art) Conventional processing of an IPv6 packet in a network.
• 3 Image of the IPway address block implemented as a shift register.
• 4 Illustration of an IPway network segment.
• 5 Illustration of the IPway package.
• 6 Flowchart of an IPway Corerouter
• 7 Processing of a packet in the corerouter within the IPway network
• 8 Packet processing when entering the IPway network.
• 9 Flowchart of an IPway Edgerouter with protocol version 1 and 2 for incoming packets
• 10 IPway packet exiting the IPway network
• 11 Flowchart of an IPway Edgerouter with protocol version 1 for outgoing packets
• 12 Flowchart of an IPway Edgerouter with protocol version 2 for outgoing packets
• 13 Mapping of a variable path length IPway packet.
• 14 Flowchart of an IPway Edgerouter with protocol version 3 for incoming packets
• 15 Flowchart of an IPway Edgerouter with protocol version 3 for incoming packets
• 16 Flowchart of an IPway Edgerouter with protocol version 3 outgoing packets
• 17 Flowchart of an IPway Edgerouter with protocol version 3 outgoing packets
• 18 Mapping of an IPway packet with IPv6 hash and IPv6 addresses.
• 19 Mapping of an IPway packet with IPv6 hash without IPv6 addresses.

literature

• [1] HG Choi et al Internet addressing architecture and hierarchical routing method thereof. U.S. Patent 6,868,416 , 2005. URL: http://www.google.com/patents/US6868416.
• [2] US Chunduri et al Accelerated MAC address resolution for IPv6 traffic with IS-IS protocol. U.S. Patent 8,934,490 , 2015. URL: https://www.google.com/patents/US8934490.
• [3] Andreas Foglar. 6Tree-Efficient IPv6 Routing. InnoRoute GmbH, 2014. URL: http://www.innoroute.com/sites/default/files/6Tree_white_paper.pdf.
• [4] J. Goldman et al. Combined Layer 2 Virtual MAC Address with Layer 3 IP Address Routing. US Patent App. 11 / 847.903 , 2009. URL: https://www.google.com/patents/US20090063706.
• [5] G. Mulligan. Method for lossless IPv6 header compression. US Patent App. 11 / 235.565 , 2006. URL: https://www.google.com/patents/ US20060088051 ,
• [6] S. Shimizu et al. Packet transfer system, communication network, and packet transfer method. US Patent App. 11 / 477.450 , 2007. URL: https://www.google.com/patents/ US20070022211 ,
• [7] Deepinder Sidhu et al. >> Open shortest path first (OSPF) routing protocol simulation <<. In: ACM SIGCOMM Computer Communication Review 23.4 (1993), pp. 53-62. URL: http://www.researchgate.net/profile/Raj_Nair4/publication/221164236_Open_Shortest_Path_First_(OSPF)_Routing_Protocol_Simulation/links/00b495386480433619000000.pdf ,
• [8] H. Wen et al. A method for reconstructing the network address in the ipv6 access network. WO Patent App. PCT / CN2006 / 001.707 , 2007. URL: http://www.google.com/patents/ WO2007028306A1 ? Cl = en.

QUOTES INCLUDE IN THE DESCRIPTION

This list of the documents listed by the applicant has been generated automatically and is included solely for the better information of the reader. The list is not part of the German patent or utility model application. The DPMA assumes no liability for any errors or omissions.

Cited non-patent literature

• Choi et al. [0001]
• Goldman et al. [0002]
• Chunduri et al. [0002]
• Who among others [0002]
• Shimizu et al. [0002]
• IPv6 standard [0003]
• Standard IPv6 Packages [0018]

Claims (6)

A method for optimizing the transmission of IP packets over IEEE 802.3 Ethernet links, further referred to as IPWay, having the following characteristics: a) removal of the MAC address from the IP packet transmitted via Ethernet, b) removal of the VLAN field from the IP packet transmitted via Ethernet, c) inserting a 256 bit way field in place of the MAC addresses, d) Rearranging the IPvX addresses in the IP packet so that the way field is followed by the destination IPvX address. A method of routing IP-WAY packets as claimed in claim 1 having the following features: using the first ld (N) bits of the routing field to determine the forwarding port, where N is the number of available ports, immediate sequential routing of the packet after the output port is known, distance the used bits from the way field, appending the identifier of the used output port to the end of the way field. A method of converting IPvX over IEEE802.3 Ethernet into IPWay frames having the following characteristics: Modification of the frame according to claim 1, obtaining the containing data and IPvX destination information, generating the path field according to claim 1 and 2. A method of converting IP-to-IPvX-over-IEEE802.3 Ethernet frames having the following characteristics: Modification of the frame according to claim 1, recovering an equivalent IPvX-over-IEEE802.3 Ethernet frame which is equivalent to the containing data Frame delivers. Device for routing in and out of an IPWay network segment, referred to as IPWay Edgerouter, having the following characteristics: Application of the methods formulated in claims 3 and 4, buffering the combination of destination address and path information of incoming packets of both directions for the accelerated processing of further packets , Device for routing within an IPWay network segment, referred to as an IPWay corerouter, having the following properties: forwarding of IPWay packets according to claim 2, accelerated forwarding compared to an unchanged IPvX frame by the features and methods described in claims 1 and 2 ,

Images