| rfc8903v2.txt | rfc8903.txt | |||
|---|---|---|---|---|
| skipping to change at line 14 ¶ | skipping to change at line 14 ¶ | |||
| Category: Informational D. Migault | Category: Informational D. Migault | |||
| ISSN: 2070-1721 Ericsson | ISSN: 2070-1721 Ericsson | |||
| R. Moskowitz | R. Moskowitz | |||
| HTT Consulting | HTT Consulting | |||
| N. Teague | N. Teague | |||
| Iron Mountain Data Centers | Iron Mountain Data Centers | |||
| L. Xia | L. Xia | |||
| Huawei | Huawei | |||
| K. Nishizuka | K. Nishizuka | |||
| NTT Communications | NTT Communications | |||
| September 2020 | May 2021 | |||
| Use Cases for DDoS Open Threat Signaling | Use Cases for DDoS Open Threat Signaling | |||
| Abstract | Abstract | |||
| The DDoS Open Threat Signaling (DOTS) effort is intended to provide | The DDoS Open Threat Signaling (DOTS) effort is intended to provide | |||
| protocols to facilitate interoperability across disparate DDoS | protocols to facilitate interoperability across disparate DDoS | |||
| Mitigation solutions. This document presents sample use cases that | Mitigation solutions. This document presents sample use cases that | |||
| describe the interactions expected between the DOTS components as | describe the interactions expected between the DOTS components as | |||
| well as DOTS messaging exchanges. These use cases are meant to | well as DOTS messaging exchanges. These use cases are meant to | |||
| skipping to change at line 46 ¶ | skipping to change at line 46 ¶ | |||
| Internet Engineering Steering Group (IESG). Not all documents | Internet Engineering Steering Group (IESG). Not all documents | |||
| approved by the IESG are candidates for any level of Internet | approved by the IESG are candidates for any level of Internet | |||
| Standard; see Section 2 of RFC 7841. | Standard; see Section 2 of RFC 7841. | |||
| Information about the current status of this document, any errata, | Information about the current status of this document, any errata, | |||
| and how to provide feedback on it may be obtained at | and how to provide feedback on it may be obtained at | |||
| https://www.rfc-editor.org/info/rfc8903. | https://www.rfc-editor.org/info/rfc8903. | |||
| Copyright Notice | Copyright Notice | |||
| Copyright (c) 2020 IETF Trust and the persons identified as the | Copyright (c) 2021 IETF Trust and the persons identified as the | |||
| document authors. All rights reserved. | document authors. All rights reserved. | |||
| This document is subject to BCP 78 and the IETF Trust's Legal | This document is subject to BCP 78 and the IETF Trust's Legal | |||
| Provisions Relating to IETF Documents | Provisions Relating to IETF Documents | |||
| (https://trustee.ietf.org/license-info) in effect on the date of | (https://trustee.ietf.org/license-info) in effect on the date of | |||
| publication of this document. Please review these documents | publication of this document. Please review these documents | |||
| carefully, as they describe your rights and restrictions with respect | carefully, as they describe your rights and restrictions with respect | |||
| to this document. Code Components extracted from this document must | to this document. Code Components extracted from this document must | |||
| include Simplified BSD License text as described in Section 4.e of | include Simplified BSD License text as described in Section 4.e of | |||
| the Trust Legal Provisions and are provided without warranty as | the Trust Legal Provisions and are provided without warranty as | |||
| End of changes. 2 change blocks. | ||||
| 2 lines changed or deleted | 2 lines changed or added | |||
This html diff was produced by rfcdiff 1.48. The latest version is available from http://tools.ietf.org/tools/rfcdiff/ | ||||