| < draft-ietf-dots-architecture-12.txt | draft-ietf-dots-architecture-13.txt > | |||
|---|---|---|---|---|
| DOTS A. Mortensen | DOTS A. Mortensen, Ed. | |||
| Internet-Draft Arbor Networks | Internet-Draft Arbor Networks | |||
| Intended status: Informational F. Andreasen | Intended status: Informational T. Reddy, Ed. | |||
| Expires: September 1, 2019 Cisco | Expires: October 5, 2019 McAfee, Inc. | |||
| T. Reddy | F. Andreasen | |||
| McAfee, Inc. | Cisco | |||
| N. Teague | N. Teague | |||
| Verisign | Verisign | |||
| R. Compton | R. Compton | |||
| Charter | Charter | |||
| C. Gray | April 03, 2019 | |||
| February 28, 2019 | ||||
| Distributed-Denial-of-Service Open Threat Signaling (DOTS) Architecture | Distributed-Denial-of-Service Open Threat Signaling (DOTS) Architecture | |||
| draft-ietf-dots-architecture-12 | draft-ietf-dots-architecture-13 | |||
| Abstract | Abstract | |||
| This document describes an architecture for establishing and | This document describes an architecture for establishing and | |||
| maintaining Distributed Denial of Service (DDoS) Open Threat | maintaining Distributed Denial of Service (DDoS) Open Threat | |||
| Signaling (DOTS) within and between domains. The document does not | Signaling (DOTS) within and between domains. The document does not | |||
| specify protocols or protocol extensions, instead focusing on | specify protocols or protocol extensions, instead focusing on | |||
| defining architectural relationships, components and concepts used in | defining architectural relationships, components and concepts used in | |||
| a DOTS deployment. | a DOTS deployment. | |||
| skipping to change at page 1, line 43 ¶ | skipping to change at page 1, line 42 ¶ | |||
| Internet-Drafts are working documents of the Internet Engineering | Internet-Drafts are working documents of the Internet Engineering | |||
| Task Force (IETF). Note that other groups may also distribute | Task Force (IETF). Note that other groups may also distribute | |||
| working documents as Internet-Drafts. The list of current Internet- | working documents as Internet-Drafts. The list of current Internet- | |||
| Drafts is at https://datatracker.ietf.org/drafts/current/. | Drafts is at https://datatracker.ietf.org/drafts/current/. | |||
| Internet-Drafts are draft documents valid for a maximum of six months | Internet-Drafts are draft documents valid for a maximum of six months | |||
| and may be updated, replaced, or obsoleted by other documents at any | and may be updated, replaced, or obsoleted by other documents at any | |||
| time. It is inappropriate to use Internet-Drafts as reference | time. It is inappropriate to use Internet-Drafts as reference | |||
| material or to cite them other than as "work in progress." | material or to cite them other than as "work in progress." | |||
| This Internet-Draft will expire on September 1, 2019. | This Internet-Draft will expire on October 5, 2019. | |||
| Copyright Notice | Copyright Notice | |||
| Copyright (c) 2019 IETF Trust and the persons identified as the | Copyright (c) 2019 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 | |||
| skipping to change at page 30, line 12 ¶ | skipping to change at page 30, line 12 ¶ | |||
| given adequate protections, again in accordance with best current | given adequate protections, again in accordance with best current | |||
| practices for network and host security. | practices for network and host security. | |||
| 6. Contributors | 6. Contributors | |||
| Mohamed Boucadair | Mohamed Boucadair | |||
| Orange | Orange | |||
| mohamed.boucadair@orange.com | mohamed.boucadair@orange.com | |||
| Christopher Gray | ||||
| Christopher_Gray3@cable.comcast.com | ||||
| 7. Acknowledgments | 7. Acknowledgments | |||
| Thanks to Matt Richardson, Roman Danyliw, Frank Xialiang, Roland | Thanks to Matt Richardson, Roman Danyliw, Frank Xialiang, Roland | |||
| Dobbins, Wei Pan, Kaname Nishizuka, Jon Shallow and Mohamed Boucadair | Dobbins, Wei Pan, Kaname Nishizuka, Jon Shallow and Mohamed Boucadair | |||
| for their comments and suggestions. | for their comments and suggestions. | |||
| 8. References | 8. References | |||
| 8.1. Normative References | 8.1. Normative References | |||
| skipping to change at page 30, line 36 ¶ | skipping to change at page 30, line 40 ¶ | |||
| [RFC8174] Leiba, B., "Ambiguity of Uppercase vs Lowercase in RFC | [RFC8174] Leiba, B., "Ambiguity of Uppercase vs Lowercase in RFC | |||
| 2119 Key Words", BCP 14, RFC 8174, DOI 10.17487/RFC8174, | 2119 Key Words", BCP 14, RFC 8174, DOI 10.17487/RFC8174, | |||
| May 2017, <https://www.rfc-editor.org/info/rfc8174>. | May 2017, <https://www.rfc-editor.org/info/rfc8174>. | |||
| 8.2. Informative References | 8.2. Informative References | |||
| [I-D.ietf-dots-requirements] | [I-D.ietf-dots-requirements] | |||
| Mortensen, A., K, R., and R. Moskowitz, "Distributed | Mortensen, A., K, R., and R. Moskowitz, "Distributed | |||
| Denial of Service (DDoS) Open Threat Signaling | Denial of Service (DDoS) Open Threat Signaling | |||
| Requirements", draft-ietf-dots-requirements-19 (work in | Requirements", draft-ietf-dots-requirements-22 (work in | |||
| progress), February 2019. | progress), March 2019. | |||
| [I-D.ietf-dots-use-cases] | [I-D.ietf-dots-use-cases] | |||
| Dobbins, R., Migault, D., Fouant, S., Moskowitz, R., | Dobbins, R., Migault, D., Fouant, S., Moskowitz, R., | |||
| Teague, N., Xia, L., and K. Nishizuka, "Use cases for DDoS | Teague, N., Xia, L., and K. Nishizuka, "Use cases for DDoS | |||
| Open Threat Signaling", draft-ietf-dots-use-cases-17 (work | Open Threat Signaling", draft-ietf-dots-use-cases-17 (work | |||
| in progress), January 2019. | in progress), January 2019. | |||
| [I-D.ietf-tls-dtls13] | [I-D.ietf-tls-dtls13] | |||
| Rescorla, E., Tschofenig, H., and N. Modadugu, "The | Rescorla, E., Tschofenig, H., and N. Modadugu, "The | |||
| Datagram Transport Layer Security (DTLS) Protocol Version | Datagram Transport Layer Security (DTLS) Protocol Version | |||
| 1.3", draft-ietf-tls-dtls13-30 (work in progress), | 1.3", draft-ietf-tls-dtls13-31 (work in progress), March | |||
| November 2018. | 2019. | |||
| [RFC0768] Postel, J., "User Datagram Protocol", STD 6, RFC 768, | [RFC0768] Postel, J., "User Datagram Protocol", STD 6, RFC 768, | |||
| DOI 10.17487/RFC0768, August 1980, | DOI 10.17487/RFC0768, August 1980, | |||
| <https://www.rfc-editor.org/info/rfc768>. | <https://www.rfc-editor.org/info/rfc768>. | |||
| [RFC0793] Postel, J., "Transmission Control Protocol", STD 7, | [RFC0793] Postel, J., "Transmission Control Protocol", STD 7, | |||
| RFC 793, DOI 10.17487/RFC0793, September 1981, | RFC 793, DOI 10.17487/RFC0793, September 1981, | |||
| <https://www.rfc-editor.org/info/rfc793>. | <https://www.rfc-editor.org/info/rfc793>. | |||
| [RFC1035] Mockapetris, P., "Domain names - implementation and | [RFC1035] Mockapetris, P., "Domain names - implementation and | |||
| skipping to change at page 33, line 21 ¶ | skipping to change at page 33, line 26 ¶ | |||
| <https://www.rfc-editor.org/info/rfc8446>. | <https://www.rfc-editor.org/info/rfc8446>. | |||
| [RFC8512] Boucadair, M., Ed., Sivakumar, S., Jacquenet, C., | [RFC8512] Boucadair, M., Ed., Sivakumar, S., Jacquenet, C., | |||
| Vinapamula, S., and Q. Wu, "A YANG Module for Network | Vinapamula, S., and Q. Wu, "A YANG Module for Network | |||
| Address Translation (NAT) and Network Prefix Translation | Address Translation (NAT) and Network Prefix Translation | |||
| (NPT)", RFC 8512, DOI 10.17487/RFC8512, January 2019, | (NPT)", RFC 8512, DOI 10.17487/RFC8512, January 2019, | |||
| <https://www.rfc-editor.org/info/rfc8512>. | <https://www.rfc-editor.org/info/rfc8512>. | |||
| Authors' Addresses | Authors' Addresses | |||
| Andrew Mortensen | Andrew Mortensen (editor) | |||
| Arbor Networks | Arbor Networks | |||
| 2727 S. State St | 2727 S. State St | |||
| Ann Arbor, MI 48104 | Ann Arbor, MI 48104 | |||
| United States | United States | |||
| EMail: andrewmortensen@gmail.com | EMail: andrewmortensen@gmail.com | |||
| Flemming Andreasen | Tirumaleswar Reddy (editor) | |||
| Cisco | ||||
| United States | ||||
| EMail: fandreas@cisco.com | ||||
| Tirumaleswar Reddy | ||||
| McAfee, Inc. | McAfee, Inc. | |||
| Embassy Golf Link Business Park | Embassy Golf Link Business Park | |||
| Bangalore, Karnataka 560071 | Bangalore, Karnataka 560071 | |||
| India | India | |||
| EMail: kondtir@gmail.com | EMail: kondtir@gmail.com | |||
| Flemming Andreasen | ||||
| Cisco | ||||
| United States | ||||
| EMail: fandreas@cisco.com | ||||
| Nik Teague | Nik Teague | |||
| Verisign | Verisign | |||
| United States | United States | |||
| EMail: nteague@verisign.com | EMail: nteague@verisign.com | |||
| Rich Compton | Rich Compton | |||
| Charter | Charter | |||
| EMail: Rich.Compton@charter.com | EMail: Rich.Compton@charter.com | |||
| Christopher Gray | ||||
| United States | ||||
| EMail: Christopher_Gray3@cable.comcast.com | ||||
| End of changes. 13 change blocks. | ||||
| 21 lines changed or deleted | 24 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/ | ||||