low-latency.md

Low Latency Intent

The low latency intent identifies the best path between a given source and destination pair based on the lowest latency. This intent is ideal for applications requiring the fastest possible connection between two points.

Network Topology

The network topology below, with the associated latency values, is used to demonstrate this intent. The latency impairments were applied using the Lab Impairment Script.

Example Scenario

In this example, Host-A (acting as a client) requests a low-latency path to Host-B (acting as a server). The HawkEye controller calculates the optimal path based on the lowest latency between the two hosts.

HawkWing Configuration

---
client_ipv6_address: 2001:db8:a::10
hawkeye:
  enabled: true
  address: 2001:db8:e5::e
  port: 10000
services:
  webserver-b:
    ipv6_addresses:
      - 2001:db8:b::10
    applications:
      - port: 80
        intents:
          - intent: low-latency

API Request

The low latency request is saved single intent folder. The JSON request format is as follows:

{
    "ipv6_source_address": "2001:db8:a::10",
    "ipv6_destination_address": "2001:db8:b::10",
    "intents": [
        {
            "type": "INTENT_TYPE_LOW_LATENCY"
        }
    ]
}

Result

The result includes the following SID List, ensuring the lowest latency path between the two hosts:

• fc00:0:1:0:1::
• fc00:0:2:0:1::
• fc00:0:4:0:1::
• fc00:0:5:0:1::
• fc00:0:6:0:1::
• fc00:0:b:0:1::

The packets are routed through the following devices: HOST-A -> SITE-A -> XR-1 -> XR-2 -> XR-4 -> XR-5 -> XR-6 -> SITE-B -> HOST-B