<?xml version="1.0" encoding="UTF-8"?>
<reference anchor="I-D.ietf-dots-architecture" target="https://datatracker.ietf.org/doc/html/draft-ietf-dots-architecture-18">
   <front>
      <title>DDoS Open Threat Signaling (DOTS) Architecture</title>
      <author initials="A." surname="Mortensen" fullname="Andrew Mortensen">
         <organization>Forcepoint</organization>
      </author>
      <author initials="T." surname="Reddy.K" fullname="Tirumaleswar Reddy.K">
         <organization>McAfee, Inc.</organization>
      </author>
      <author initials="F." surname="Andreasen" fullname="Flemming Andreasen">
         <organization>Cisco</organization>
      </author>
      <author initials="N." surname="Teague" fullname="Nik Teague">
         <organization>Iron Mountain</organization>
      </author>
      <author initials="R." surname="Compton" fullname="Rich Compton">
         <organization>Charter</organization>
      </author>
      <date month="March" day="6" year="2020" />
      <abstract>
	 <t>This document describes an architecture for establishing and maintaining Distributed Denial-of-Service (DDoS) Open Threat Signaling (DOTS) within and between domains.  The document does not specify protocols or protocol extensions, instead focusing on defining architectural relationships, components, and concepts used in a DOTS deployment.
	 </t>
      </abstract>
   </front>
   <seriesInfo name="Internet-Draft" value="draft-ietf-dots-architecture-18" />
   
</reference>
