<?xml version="1.0" encoding="UTF-8"?>
<reference anchor="I-D.verma-dmsc-nlip-notes" target="https://datatracker.ietf.org/doc/html/draft-verma-dmsc-nlip-notes-00">
   <front>
      <title>Use of Natural Language for Agent Communication</title>
      <author initials="D. C." surname="Verma" fullname="Dinesh C. Verma">
         <organization>IBM</organization>
      </author>
      <author initials="E." surname="Bertino" fullname="Elisa Bertino">
         <organization>Purdue University</organization>
      </author>
      <author initials="A." surname="Ratnaparkhi" fullname="Abhay Ratnaparkhi">
         <organization>eBay Inc.</organization>
      </author>
      <author initials="S." surname="Hughes" fullname="Sean Hughes">
         <organization>Service Now</organization>
      </author>
      <author initials="L." surname="Xing" fullname="Luyi Xing">
         <organization>University of Illinois at Urbana-Champaign</organization>
      </author>
      <author initials="Z." surname="Li" fullname="Zichuan Li">
         <organization>University of Illinois at Urbana-Champaign</organization>
      </author>
      <author initials="X." surname="Liao" fullname="Xiaojing Liao">
         <organization>University of Illinois at Urbana-Champaign</organization>
      </author>
      <author initials="J." surname="Cui" fullname="Jian Cui">
         <organization>University of Illinois at Urbana-Champaign</organization>
      </author>
      <author initials="R." surname="Topaloglu" fullname="Rasit Topaloglu">
         <organization>Marist University</organization>
      </author>
      <author initials="M." surname="Rahouti" fullname="Mohamed Rahouti">
         <organization>Fordham University</organization>
      </author>
      <date month="February" day="11" year="2026" />
      <abstract>
	 <t>   In current communication protocol designs, the prevalent practice is
   to define a strict Application Programming Interface (API) for
   different types of interactions among software entities.  There is an
   explosion of APIs which makes interoperability hard, and the
   standards for interoperability fragile.  Specifically for agent to
   agent communications, defining strict APIs for interactions such as
   registration, discovery, telemetry and debugging creates significant
   operational challenges.  In this draft, we argue that a flexible
   design option -- where generative AI is used to create a flexible
   communication protocol for APIs, can lead to a common and flexible
   way for a single uniform API to be used between agents, and enables a
   better communication paradigm.

	 </t>
      </abstract>
   </front>
   <seriesInfo name="Internet-Draft" value="draft-verma-dmsc-nlip-notes-00" />
   
</reference>
