<?xml version="1.0" encoding="UTF-8"?>
<reference anchor="I-D.ietf-dots-use-cases" target="https://datatracker.ietf.org/doc/html/draft-ietf-dots-use-cases-07">
   <front>
      <title>Use cases for DDoS Open Threat Signaling</title>
      <author initials="R." surname="Dobbins" fullname="Roland Dobbins">
         <organization>Arbor Networks</organization>
      </author>
      <author initials="D." surname="Migault" fullname="Daniel Migault">
         <organization>Ericsson</organization>
      </author>
      <author initials="S." surname="Fouant" fullname="Stefan Fouant">
         </author>
      <author initials="R." surname="Moskowitz" fullname="Robert Moskowitz">
         <organization>HTT Consulting</organization>
      </author>
      <author initials="N." surname="Teague" fullname="Nik Teague">
         <organization>Verisign</organization>
      </author>
      <author initials="L." surname="Xia" fullname="Liang Xia">
         <organization>Huawei</organization>
      </author>
      <author initials="K." surname="Nishizuka" fullname="Kaname Nishizuka">
         <organization>NTT Communications</organization>
      </author>
      <date month="July" day="20" year="2017" />
      <abstract>
	 <t>   The DDoS Open Threat Signaling (DOTS) effort is intended to provide a
   protocol that facilitates interoperability between multivendor
   solutions/services.  This document presents use cases to evaluate the
   interactions expected between the DOTS components as well as DOTS
   messaging exchanges.  The purpose of describing use cases is to
   identify the interacting DOTS components, how they collaborate and
   what are the types of information to be exchanged.

	 </t>
      </abstract>
   </front>
   <seriesInfo name="Internet-Draft" value="draft-ietf-dots-use-cases-07" />
   
</reference>
