<?xml version="1.0" encoding="UTF-8"?>
<reference anchor="I-D.ietf-cdni-ci-triggers-rfc8007bis" target="https://datatracker.ietf.org/doc/html/draft-ietf-cdni-ci-triggers-rfc8007bis-19">
   <front>
      <title>Content Delivery Network Interconnection (CDNI) Control Interface / Triggers 2nd Edition</title>
      <author initials="N. B." surname="Sopher" fullname="Nir Baruch Sopher">
         <organization>Qwilt</organization>
      </author>
      <author initials="O." surname="Finkelman" fullname="Ori Finkelman">
         <organization>Qwilt</organization>
      </author>
      <author initials="S." surname="Mishra" fullname="Sanjay Mishra">
         <organization>Verizon</organization>
      </author>
      <author initials="J. K." surname="Robertson" fullname="Jay K. Robertson">
         <organization>Qwilt</organization>
      </author>
      <author initials="A." surname="Arolovitch" fullname="Alan Arolovitch">
         <organization>2you.io</organization>
      </author>
      <date month="March" day="2" year="2026" />
      <abstract>
	 <t>   This document obsoletes RFC8007.  The document describes the part of
   Content Delivery Network Interconnection (CDNI) Control interface
   that allows a CDN to trigger activity in an interconnected CDN that
   is configured to deliver content on its behalf.  The upstream CDN MAY
   use this mechanism to request that the downstream CDN preposition,
   invalidate, and/or purge metadata and/or content.  The upstream CDN
   MAY monitor the status of activity that it has triggered in the
   downstream CDN.

	 </t>
      </abstract>
   </front>
   <seriesInfo name="Internet-Draft" value="draft-ietf-cdni-ci-triggers-rfc8007bis-19" />
   
</reference>
