<?xml version="1.0" encoding="UTF-8"?>
<reference anchor="I-D.jain-lisp-network-ai-infra" target="https://datatracker.ietf.org/doc/html/draft-jain-lisp-network-ai-infra-04">
   <front>
      <title>LISP-Based Network for AI Infrastructure</title>
      <author initials="P." surname="Jain" fullname="Prakash Jain">
         <organization>Celestica</organization>
      </author>
      <author initials="S." surname="Hooda" fullname="Sanjay Hooda">
         <organization>Cisco Systems</organization>
      </author>
      <author initials="D." surname="Srivastava" fullname="Durgesh Srivastava">
         <organization>DataraAI</organization>
      </author>
      <author initials="P." surname="Pillay-Esnault" fullname="Padma Pillay-Esnault">
         <organization>Independent</organization>
      </author>
      <author initials="V." surname="Moreno" fullname="Victor Moreno">
         <organization>Google</organization>
      </author>
      <date month="June" day="17" year="2026" />
      <abstract>
	 <t>   The Locator/Identifier Separation Protocol (LISP) control plane
   provides the mechanisms to support Scale-Up, Scale-Out and Scale-
   Across backend networks within AI infrastructure.  This document
   describes how LISP enables a unified control plane architecture that
   accommodates different scaling technologies, offering flexibility in
   deployment.  By leveraging lisp mechanisms including EID-to-RLOC-
   mapping/pxTR registrations, publication-subscription and VPN
   instance-based segmentation ([RFC9300][RFC9301][RFC9437][I-D.ietf-
   lisp-site-external-connectivity][I-D.ietf-lisp-vpn]), the
   architecture delivers scalable high bandwidth for large training
   workloads, ultra-low-latency collective operations, and a simplified
   control framework that seamlessly spans heterogeneous accelerator
   fabrics.  This approach allows AI/ML applications (whether focused on
   training or inference) to run workloads efficiently with resiliency
   on a converged infrastructure, supporting diverse deployment
   scenarios using the same underlying network fabric.


	 </t>
      </abstract>
   </front>
   <seriesInfo name="Internet-Draft" value="draft-jain-lisp-network-ai-infra-04" />
   
</reference>
