Source routing

In computer networking, source routing, also called path addressing, allows a sender of a packet to partially or completely specify the route the packet takes through the network.[1] In contrast, in conventional routing, routers in the network determine the path incrementally based on the packet's destination. Another routing alternative, label switching, is used in connection-oriented networks such as X.25, Frame Relay, Asynchronous Transfer Mode and Multiprotocol Label Switching.

Source routing allows easier troubleshooting, improved traceroute, and enables a node to discover all the possible routes to a host. It does not allow a source to directly manage network performance by forcing packets to travel over one path to prevent congestion on another.

Many high-performance interconnects including Myrinet, Quadrics,[2] IEEE 1355, and SpaceWire support source routing.

Internet Protocol

In the Internet Protocol, two header options are available which are rarely used: "strict source and record route" (SSRR) and "loose source and record route" (LSRR).[3] Because of security concerns, packets marked LSRR are frequently blocked on the Internet. If not blocked, LSRR can allow an attacker to spoof an address but still successfully receive response packets by forcing return traffic for spoofed packets to return through the attacker's device.[4]

In IPv6, two forms of source routing have been developed. The first approach was the Type 0 Routing header.[5] This routing header was designed to support the same use cases as the IPv4 header options. Unfortunately there were several significant attacks against this routing header and its utilisation was deprecated.[6] A more secure form of source routing is being developed within the IETF to support the IPv6 version of Segment Routing.[7]

Software-defined networking

Software-defined networking can also be enhanced when source routing is used in the forwarding plane. Studies have shown significant improvements in convergence times as a result of the reduced state that must be distributed by the controller into the network.[8][9]

Myrinet

When using source routing with Myrinet, the sender of the packet prepends the complete route, one byte for every crossbar, to each packet header. Each crossbar examines the first routing byte of the packet. When using source routing, that byte indicates a particular port of that crossbar; when that port becomes available, the router discards that routing byte and sends the rest of the packet out that port.[2]

SpaceWire

Each packet traveling through a SpaceWire network can use path addressing (source routing) or logical addressing or some combination. The router examines the first data character of the packet; when it indicates some specific port of the router, the router discards that routing character and sends the rest of the packet out that port.[10][11][12]

gollark: I'll edit that.
gollark: I'm also going to make nil not equal nil.
gollark: Anyway, I'm going to make attempt to index nil a thing of the past! Instead it'll be "WHY IS MY PROGRAM ACCESSING POTATOS DATA".
gollark: Unary minus on strings?
gollark: YEEES, let the JS flow through you.

See also

References
  1. Carl A. Sunshine, Source routing in computer networks, p. 29
  2. Patrick Geoffray; Torsten Hoefler, Adaptive Routing Strategies for Modern High Performance Networks (PDF), p. 2
  3. Internet Protocol. IETF. September 1981. doi:10.17487/RFC0791. RFC 791.
  4. Rik Farrow. "Source Address Spoofing".
  5. Deering, S.; Hinden, R. (December 1998). Internet Protocol, Version 6 (IPv6) Specification. IETF. doi:10.17487/RFC2460. RFC 2460.
  6. Abley, J. (December 2007). Deprecation of Type 0 Routing Headers in IPv6. IETF. doi:10.17487/RFC5095. RFC 5095.
  7. Previdi, S. (Ed.) (July 2017). IPv6 Segment Routing Header (SRH). IETF. I-D draft-ietf-6man-segment-routing-header-07.CS1 maint: extra text: authors list (link)
  8. Mourad Soliman. "SDN and Source Routing" (PDF). SIGCOMM.
  9. Peter Ashwood-Smith. "SDN State Reduction" (PDF). IETF.
  10. Steve Parkes. "SpaceWire User’s Guide". 2012. p. 20.
  11. Paul Walker, Barry Cook. "SpaceWire: Key principles brought out from 40 year history". 2006. p. 5.
  12. S.M. Parkes and C. McClements. "SpaceWire Networks". 2002. page 61.4.
This article is issued from Wikipedia. The text is licensed under Creative Commons - Attribution - Sharealike. Additional terms may apply for the media files.