LISP Map Server Policy Change Notification
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
In Locator ID Separation Protocol (LISP) based software-defined networks, existing implementations face challenges in efficiently and scalably propagating policy changes to all network nodes, leading to potential information loss, security risks, and communication errors due to stale routing policies.
Innovation Solution
A map server (MSMR) is configured to generate and transmit selective and collective LISP mapping notifications to only affected edge or border devices, tracking registered EIDs and prefixes, and using a publisher-subscriber mechanism to ensure immediate policy updates, thereby avoiding broadcast to all nodes and reducing security risks.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Speed
If a broad stroke approach is used to instantly communicate all policy changes to all network nodes, then policy propagation speed is improved, but network overhead and resource consumption increase significantly
Solution Approach 1:
The patent segments the network into LISP domains and further segments policy notification into selective groups of RLOCs within each domain. Instead of broadcasting to all nodes, the system divides the notification task into smaller targeted segments, sending policy changes only to affected RLOCs in specific LISP domains, thereby reducing overall network overhead while maintaining fast propagation.
Solution Approach 2:
The patent applies local quality by sending customized policy notifications to specific LISP domains based on their particular needs and affected EIDs. Each LISP domain receives policy changes tailored to its local context - only the RLOCs within domains that have affected EIDs receive notifications, rather than a uniform broadcast to all nodes. This localized approach optimizes resource usage while ensuring timely policy propagation.
2Loss of energy
If policy changes are not propagated timely to all routers, then network resource consumption is reduced, but routing correctness and security are compromised
Solution Approach 1:
The system performs preliminary action by pre-establishing the relationship between EIDs and their corresponding LISP domains before policy changes occur. When a policy change is detected, the system can immediately identify which LISP domains and which specific RLOCs within those domains are affected, enabling rapid targeted notification without the need for broad broadcasting, thus maintaining routing correctness with minimal resource consumption.
Solution Approach 2:
The patent implements feedback mechanisms where LISP routers provide information about their EID mappings and domain affiliations to the policy management system. This feedback enables the system to accurately determine which RLOCs need policy updates, ensuring that policy changes are propagated reliably to the correct nodes without unnecessary transmissions, thereby maintaining routing correctness while optimizing resource usage.
3Quantity of substance
If selective notification to affected nodes is implemented, then network overhead is reduced, but system complexity increases due to tracking and identification mechanisms
Solution Approach 1:
The patent applies universality by designing the LISP infrastructure to serve multiple functions: the existing LISP mapping system not only performs address translation but also provides the framework for policy change notification. The LISP domains, EID mappings, and RLOC relationships that already exist for routing purposes are leveraged to identify and notify affected nodes, eliminating the need for separate tracking infrastructure and reducing overall system complexity.
Solution Approach 2:
The patent introduces an intermediary mechanism in the form of LISP domain controllers or border routers that facilitate policy change propagation. These intermediaries receive policy changes from the policy management system, determine which RLOCs within their domain are affected based on existing EID mappings, and forward notifications accordingly. This intermediary approach simplifies the overall system by distributing the tracking and notification logic across existing LISP infrastructure components rather than requiring a centralized complex tracking system.
Data Source
Figure 1
Figure 2
Figure 3
AI summary
Systems, methods, and computer-readable media for communicating policy changes in a Locator/ID Separation Protocol (LISP) based network deployment include receiving, at a first routing device, a first notification from a map server, the first notification indicating a change in a policy for LISP based communication between at least a first endpoint device and at least a second endpoint device, the first endpoint device being connected to a network fabric through the first routing device and the second endpoint device being connected to the network fabric through a second routing device. The first routing device forwards a second notification to the second routing device if one or more entries of a first map cache implemented by the first routing device are affected by the policy change, the second notification indicating a set of one or more endpoints connected to the second routing device that are affected by the policy change.