| rfc9244v4.txt | rfc9244.txt | |||
|---|---|---|---|---|
| Internet Engineering Task Force (IETF) M. Boucadair, Ed. | Internet Engineering Task Force (IETF) M. Boucadair, Ed. | |||
| Request for Comments: 9244 Orange | Request for Comments: 9244 Orange | |||
| Category: Standards Track T. Reddy.K, Ed. | Category: Standards Track T. Reddy.K, Ed. | |||
| ISSN: 2070-1721 Akamai | ISSN: 2070-1721 Akamai | |||
| E. Doron | E. Doron | |||
| Radware Ltd. | Radware Ltd. | |||
| M. Chen | M. Chen | |||
| CMCC | CMCC | |||
| J. Shallow | J. Shallow | |||
| May 2022 | June 2022 | |||
| Distributed Denial-of-Service Open Threat Signaling (DOTS) Telemetry | Distributed Denial-of-Service Open Threat Signaling (DOTS) Telemetry | |||
| Abstract | Abstract | |||
| This document aims to enrich the Distributed Denial-of-Service Open | This document aims to enrich the Distributed Denial-of-Service Open | |||
| Threat Signaling (DOTS) signal channel protocol with various | Threat Signaling (DOTS) signal channel protocol with various | |||
| telemetry attributes, allowing for optimal Distributed Denial-of- | telemetry attributes, allowing for optimal Distributed Denial-of- | |||
| Service (DDoS) attack mitigation. It specifies the normal traffic | Service (DDoS) attack mitigation. It specifies the normal traffic | |||
| baseline and attack traffic telemetry attributes a DOTS client can | baseline and attack traffic telemetry attributes a DOTS client can | |||
| skipping to change at line 1453 ¶ | skipping to change at line 1453 ¶ | |||
| to the target. | to the target. | |||
| * The maximum number of simultaneous connections that are allowed | * The maximum number of simultaneous connections that are allowed | |||
| to the target per client. | to the target per client. | |||
| * The maximum number of simultaneous embryonic connections that | * The maximum number of simultaneous embryonic connections that | |||
| are allowed to the target. The term "embryonic connection" | are allowed to the target. The term "embryonic connection" | |||
| refers to a connection whose connection handshake is not | refers to a connection whose connection handshake is not | |||
| finished. Embryonic connections are only possible in | finished. Embryonic connections are only possible in | |||
| connection-oriented transport protocols like TCP or the Stream | connection-oriented transport protocols like TCP or the Stream | |||
| Control Transmission Protocol (SCTP) [RFC4960]. | Control Transmission Protocol (SCTP) [RFC9260]. | |||
| * The maximum number of simultaneous embryonic connections that | * The maximum number of simultaneous embryonic connections that | |||
| are allowed to the target per client. | are allowed to the target per client. | |||
| * The maximum number of connections allowed per second to the | * The maximum number of connections allowed per second to the | |||
| target. | target. | |||
| * The maximum number of connections allowed per second to the | * The maximum number of connections allowed per second to the | |||
| target per client. | target per client. | |||
| skipping to change at line 4040 ¶ | skipping to change at line 4040 ¶ | |||
| "IANA: Private Enterprise Numbers | "IANA: Private Enterprise Numbers | |||
| (https://www.iana.org/assignments/enterprise-numbers/)"; | (https://www.iana.org/assignments/enterprise-numbers/)"; | |||
| } | } | |||
| leaf attack-id { | leaf attack-id { | |||
| type uint32; | type uint32; | |||
| description | description | |||
| "Unique identifier assigned by the vendor for the attack."; | "Unique identifier assigned by the vendor for the attack."; | |||
| } | } | |||
| leaf description-lang { | leaf description-lang { | |||
| type string { | type string { | |||
| pattern '(([A-Za-z]{2,3}(-[A-Za-z]{3}(-[A-Za-z]{3})' | pattern '((([A-Za-z]{2,3}(-[A-Za-z]{3}(-[A-Za-z]{3})' | |||
| + '{0,2})?|[A-Za-z]{4}|[A-Za-z]{5,8})(-[A-Za-z]{4})?' | + '{0,2})?)|[A-Za-z]{4}|[A-Za-z]{5,8})(-[A-Za-z]{4})' | |||
| + '(-([A-Za-z]{2}|[0-9]{3}))?(-([A-Za-z0-9]{5,8}' | + '?(-([A-Za-z]{2}|[0-9]{3}))?(-([A-Za-z0-9]{5,8}' | |||
| + '|([0-9][A-Za-z0-9]{3})))*(-[0-9A-WY-Za-wy-z]' | + '|([0-9][A-Za-z0-9]{3})))*(-[0-9A-WYZa-wyz]' | |||
| + '(-([A-Za-z0-9]{2,8}))+)*(-[Xx](-([A-Za-z0-9]' | + '(-([A-Za-z0-9]{2,8}))+)*(-[Xx](-([A-Za-z0-9]' | |||
| + '{1,8}))+)?|[Xx](-([A-Za-z0-9]{1,8}))+|' | + '{1,8}))+)?|[Xx](-([A-Za-z0-9]{1,8}))+|' | |||
| + '(([Ee][Nn]-[Gg][Bb]-[Oo][Ee][Dd]|[Ii]-' | + '(([Ee][Nn]-[Gg][Bb]-[Oo][Ee][Dd]|[Ii]-' | |||
| + '[Aa][Mm][Ii]|[Ii]-[Bb][Nn][Nn]|[Ii]-' | + '[Aa][Mm][Ii]|[Ii]-[Bb][Nn][Nn]|[Ii]-' | |||
| + '[Dd][Ee][Ff][Aa][Uu][Ll][Tt]|[Ii]-' | + '[Dd][Ee][Ff][Aa][Uu][Ll][Tt]|[Ii]-' | |||
| + '[Ee][Nn][Oo][Cc][Hh][Ii][Aa][Nn]' | + '[Ee][Nn][Oo][Cc][Hh][Ii][Aa][Nn]' | |||
| + '|[Ii]-[Hh][Aa][Kk]|' | + '|[Ii]-[Hh][Aa][Kk]|' | |||
| + '[Ii]-[Kk][Ll][Ii][Nn][Gg][Oo][Nn]|' | + '[Ii]-[Kk][Ll][Ii][Nn][Gg][Oo][Nn]|' | |||
| + '[Ii]-[Ll][Uu][Xx]|[Ii]-[Mm][Ii][Nn][Gg][Oo]|' | + '[Ii]-[Ll][Uu][Xx]|[Ii]-[Mm][Ii][Nn][Gg][Oo]|' | |||
| + '[Ii]-[Nn][Aa][Vv][Aa][Jj][Oo]|[Ii]-[Pp][Ww][Nn]|' | + '[Ii]-[Nn][Aa][Vv][Aa][Jj][Oo]|[Ii]-[Pp][Ww][Nn]|' | |||
| skipping to change at line 4707 ¶ | skipping to change at line 4707 ¶ | |||
| "IANA: Private Enterprise Numbers | "IANA: Private Enterprise Numbers | |||
| (https://www.iana.org/assignments/enterprise-numbers/)"; | (https://www.iana.org/assignments/enterprise-numbers/)"; | |||
| } | } | |||
| leaf vendor-name { | leaf vendor-name { | |||
| type string; | type string; | |||
| description | description | |||
| "The name of the vendor (e.g., company A)."; | "The name of the vendor (e.g., company A)."; | |||
| } | } | |||
| leaf description-lang { | leaf description-lang { | |||
| type string { | type string { | |||
| pattern '(([A-Za-z]{2,3}(-[A-Za-z]{3}(-[A-Za-z]{3})' | pattern '((([A-Za-z]{2,3}(-[A-Za-z]{3}(-[A-Za-z]{3})' | |||
| + '{0,2})?|[A-Za-z]{4}|[A-Za-z]{5,8})(-[A-Za-z]{4})?' | + '{0,2})?)|[A-Za-z]{4}|[A-Za-z]{5,8})(-[A-Za-z]{4})' | |||
| + '(-([A-Za-z]{2}|[0-9]{3}))?(-([A-Za-z0-9]{5,8}' | + '?(-([A-Za-z]{2}|[0-9]{3}))?(-([A-Za-z0-9]{5,8}' | |||
| + '|([0-9][A-Za-z0-9]{3})))*(-[0-9A-WY-Za-wy-z]' | + '|([0-9][A-Za-z0-9]{3})))*(-[0-9A-WYZa-wyz]' | |||
| + '(-([A-Za-z0-9]{2,8}))+)*(-[Xx](-([A-Za-z0-9]' | + '(-([A-Za-z0-9]{2,8}))+)*(-[Xx](-([A-Za-z0-9]' | |||
| + '{1,8}))+)?|[Xx](-([A-Za-z0-9]{1,8}))+|' | + '{1,8}))+)?|[Xx](-([A-Za-z0-9]{1,8}))+|' | |||
| + '(([Ee][Nn]-[Gg][Bb]-[Oo][Ee][Dd]|[Ii]-' | + '(([Ee][Nn]-[Gg][Bb]-[Oo][Ee][Dd]|[Ii]-' | |||
| + '[Aa][Mm][Ii]|[Ii]-[Bb][Nn][Nn]|[Ii]-' | + '[Aa][Mm][Ii]|[Ii]-[Bb][Nn][Nn]|[Ii]-' | |||
| + '[Dd][Ee][Ff][Aa][Uu][Ll][Tt]|[Ii]-' | + '[Dd][Ee][Ff][Aa][Uu][Ll][Tt]|[Ii]-' | |||
| + '[Ee][Nn][Oo][Cc][Hh][Ii][Aa][Nn]' | + '[Ee][Nn][Oo][Cc][Hh][Ii][Aa][Nn]' | |||
| + '|[Ii]-[Hh][Aa][Kk]|' | + '|[Ii]-[Hh][Aa][Kk]|' | |||
| + '[Ii]-[Kk][Ll][Ii][Nn][Gg][Oo][Nn]|' | + '[Ii]-[Kk][Ll][Ii][Nn][Gg][Oo][Nn]|' | |||
| + '[Ii]-[Ll][Uu][Xx]|[Ii]-[Mm][Ii][Nn][Gg][Oo]|' | + '[Ii]-[Ll][Uu][Xx]|[Ii]-[Mm][Ii][Nn][Gg][Oo]|' | |||
| + '[Ii]-[Nn][Aa][Vv][Aa][Jj][Oo]|[Ii]-[Pp][Ww][Nn]|' | + '[Ii]-[Nn][Aa][Vv][Aa][Jj][Oo]|[Ii]-[Pp][Ww][Nn]|' | |||
| skipping to change at line 5514 ¶ | skipping to change at line 5514 ¶ | |||
| [RFC2330] Paxson, V., Almes, G., Mahdavi, J., and M. Mathis, | [RFC2330] Paxson, V., Almes, G., Mahdavi, J., and M. Mathis, | |||
| "Framework for IP Performance Metrics", RFC 2330, | "Framework for IP Performance Metrics", RFC 2330, | |||
| DOI 10.17487/RFC2330, May 1998, | DOI 10.17487/RFC2330, May 1998, | |||
| <https://www.rfc-editor.org/info/rfc2330>. | <https://www.rfc-editor.org/info/rfc2330>. | |||
| [RFC4732] Handley, M., Ed., Rescorla, E., Ed., and IAB, "Internet | [RFC4732] Handley, M., Ed., Rescorla, E., Ed., and IAB, "Internet | |||
| Denial-of-Service Considerations", RFC 4732, | Denial-of-Service Considerations", RFC 4732, | |||
| DOI 10.17487/RFC4732, December 2006, | DOI 10.17487/RFC4732, December 2006, | |||
| <https://www.rfc-editor.org/info/rfc4732>. | <https://www.rfc-editor.org/info/rfc4732>. | |||
| [RFC4960] Stewart, R., Ed., "Stream Control Transmission Protocol", | ||||
| RFC 4960, DOI 10.17487/RFC4960, September 2007, | ||||
| <https://www.rfc-editor.org/info/rfc4960>. | ||||
| [RFC5612] Eronen, P. and D. Harrington, "Enterprise Number for | [RFC5612] Eronen, P. and D. Harrington, "Enterprise Number for | |||
| Documentation Use", RFC 5612, DOI 10.17487/RFC5612, August | Documentation Use", RFC 5612, DOI 10.17487/RFC5612, August | |||
| 2009, <https://www.rfc-editor.org/info/rfc5612>. | 2009, <https://www.rfc-editor.org/info/rfc5612>. | |||
| [RFC8340] Bjorklund, M. and L. Berger, Ed., "YANG Tree Diagrams", | [RFC8340] Bjorklund, M. and L. Berger, Ed., "YANG Tree Diagrams", | |||
| BCP 215, RFC 8340, DOI 10.17487/RFC8340, March 2018, | BCP 215, RFC 8340, DOI 10.17487/RFC8340, March 2018, | |||
| <https://www.rfc-editor.org/info/rfc8340>. | <https://www.rfc-editor.org/info/rfc8340>. | |||
| [RFC8525] Bierman, A., Bjorklund, M., Schoenwaelder, J., Watsen, K., | [RFC8525] Bierman, A., Bjorklund, M., Schoenwaelder, J., Watsen, K., | |||
| and R. Wilton, "YANG Library", RFC 8525, | and R. Wilton, "YANG Library", RFC 8525, | |||
| skipping to change at line 5557 ¶ | skipping to change at line 5553 ¶ | |||
| "Controlling Filtering Rules Using Distributed Denial-of- | "Controlling Filtering Rules Using Distributed Denial-of- | |||
| Service Open Threat Signaling (DOTS) Signal Channel", | Service Open Threat Signaling (DOTS) Signal Channel", | |||
| RFC 9133, DOI 10.17487/RFC9133, September 2021, | RFC 9133, DOI 10.17487/RFC9133, September 2021, | |||
| <https://www.rfc-editor.org/info/rfc9133>. | <https://www.rfc-editor.org/info/rfc9133>. | |||
| [RFC9177] Boucadair, M. and J. Shallow, "Constrained Application | [RFC9177] Boucadair, M. and J. Shallow, "Constrained Application | |||
| Protocol (CoAP) Block-Wise Transfer Options Supporting | Protocol (CoAP) Block-Wise Transfer Options Supporting | |||
| Robust Transmission", RFC 9177, DOI 10.17487/RFC9177, | Robust Transmission", RFC 9177, DOI 10.17487/RFC9177, | |||
| March 2022, <https://www.rfc-editor.org/info/rfc9177>. | March 2022, <https://www.rfc-editor.org/info/rfc9177>. | |||
| [RFC9260] Stewart, R., Tüxen, M., and K. Nielsen, "Stream Control | ||||
| Transmission Protocol", RFC 9260, DOI 10.17487/RFC9260, | ||||
| June 2022, <https://www.rfc-editor.org/info/rfc9260>. | ||||
| Acknowledgments | Acknowledgments | |||
| The authors would like to thank Flemming Andreasen, Liang Xia, and | The authors would like to thank Flemming Andreasen, Liang Xia, and | |||
| Kaname Nishizuka, coauthors of [DOTS-Telemetry-Specs], and everyone | Kaname Nishizuka, coauthors of [DOTS-Telemetry-Specs], and everyone | |||
| who had contributed to that document. | who had contributed to that document. | |||
| Thanks to Kaname Nishizuka, Yuhei Hayashi, and Tom Petch for comments | Thanks to Kaname Nishizuka, Yuhei Hayashi, and Tom Petch for comments | |||
| and review. | and review. | |||
| Special thanks to Jon Shallow and Kaname Nishizuka for their | Special thanks to Jon Shallow and Kaname Nishizuka for their | |||
| End of changes. 6 change blocks. | ||||
| 14 lines changed or deleted | 14 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/ | ||||