< draft-ietf-dots-signal-channel-37.txt		draft-ietf-dots-signal-channel-38.txt >
	DOTS T. Reddy, Ed.		DOTS T. Reddy, Ed.
	Internet-Draft McAfee		Internet-Draft McAfee
	Intended status: Standards Track M. Boucadair, Ed.		Intended status: Standards Track M. Boucadair, Ed.
	Expires: January 29, 2020 Orange		Expires: April 20, 2020 Orange
	P. Patil		P. Patil
	Cisco		Cisco
	A. Mortensen		A. Mortensen
	Arbor Networks, Inc.		Arbor Networks, Inc.
	N. Teague		N. Teague
	Iron Mountain Data Centers		Iron Mountain Data Centers
	July 28, 2019		October 18, 2019
	Distributed Denial-of-Service Open Threat Signaling (DOTS) Signal		Distributed Denial-of-Service Open Threat Signaling (DOTS) Signal
	Channel Specification		Channel Specification
	draft-ietf-dots-signal-channel-37		draft-ietf-dots-signal-channel-38
	Abstract		Abstract
	This document specifies the DOTS signal channel, a protocol for		This document specifies the DOTS signal channel, a protocol for
	signaling the need for protection against Distributed Denial-of-		signaling the need for protection against Distributed Denial-of-
	Service (DDoS) attacks to a server capable of enabling network		Service (DDoS) attacks to a server capable of enabling network
	traffic mitigation on behalf of the requesting client.		traffic mitigation on behalf of the requesting client.
	A companion document defines the DOTS data channel, a separate		A companion document defines the DOTS data channel, a separate
	reliable communication layer for DOTS management and configuration		reliable communication layer for DOTS management and configuration
	skipping to change at page 2, line 25 ¶		skipping to change at page 2, line 25 ¶
	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 January 29, 2020.		This Internet-Draft will expire on April 20, 2020.
	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 20, line 46 ¶		skipping to change at page 20, line 46 ¶
	Only single-valued 'cdid' are defined in this document. That		Only single-valued 'cdid' are defined in this document. That
	is, only the first on-path server-domain DOTS gateway can		is, only the first on-path server-domain DOTS gateway can
	insert a 'cdid' value. This specification does not allow		insert a 'cdid' value. This specification does not allow
	multiple server-domain DOTS gateways, whenever involved in the		multiple server-domain DOTS gateways, whenever involved in the
	path, to insert a 'cdid' value for each server-domain gateway.		path, to insert a 'cdid' value for each server-domain gateway.
	This is an optional Uri-Path. When present, 'cdid' MUST be		This is an optional Uri-Path. When present, 'cdid' MUST be
	positioned before 'cuid'.		positioned before 'cuid'.
	A DOTS gateway MAY add the CoAP Hop-Limit Option		A DOTS gateway SHOULD add the CoAP Hop-Limit Option
	[I-D.ietf-core-hop-limit].		[I-D.ietf-core-hop-limit].
	Because of the complexity to handle partial failure cases, this		Because of the complexity to handle partial failure cases, this
	specification does not allow for including multiple mitigation		specification does not allow for including multiple mitigation
	requests in the same PUT request. Concretely, a DOTS client MUST NOT		requests in the same PUT request. Concretely, a DOTS client MUST NOT
	include multiple entries in the 'scope' array of the same PUT		include multiple entries in the 'scope' array of the same PUT
	request.		request.
	FQDN and URI mitigation scopes may be thought of as a form of scope		FQDN and URI mitigation scopes may be thought of as a form of scope
	alias, in which the addresses associated with the domain name or URI		alias, in which the addresses associated with the domain name or URI
	skipping to change at page 97, line 32 ¶		skipping to change at page 97, line 32 ¶
	Thanks to Alexey Melnikov, Adam Roach, Suresh Krishnan, Mirja		Thanks to Alexey Melnikov, Adam Roach, Suresh Krishnan, Mirja
	Kuehlewind, and Alissa Cooper for the review.		Kuehlewind, and Alissa Cooper for the review.
	13. References		13. References
	13.1. Normative References		13.1. Normative References
	[I-D.ietf-core-hop-limit]		[I-D.ietf-core-hop-limit]
	Boucadair, M., K, R., and J. Shallow, "Constrained		Boucadair, M., K, R., and J. Shallow, "Constrained
	Application Protocol (CoAP) Hop-Limit Option", draft-ietf-		Application Protocol (CoAP) Hop-Limit Option", draft-ietf-
	core-hop-limit-04 (work in progress), July 2019.		core-hop-limit-07 (work in progress), October 2019.
	[RFC0791] Postel, J., "Internet Protocol", STD 5, RFC 791,		[RFC0791] Postel, J., "Internet Protocol", STD 5, RFC 791,
	DOI 10.17487/RFC0791, September 1981,		DOI 10.17487/RFC0791, September 1981,
	<https://www.rfc-editor.org/info/rfc791>.		<https://www.rfc-editor.org/info/rfc791>.
	[RFC1122] Braden, R., Ed., "Requirements for Internet Hosts -		[RFC1122] Braden, R., Ed., "Requirements for Internet Hosts -
	Communication Layers", STD 3, RFC 1122,		Communication Layers", STD 3, RFC 1122,
	DOI 10.17487/RFC1122, October 1989,		DOI 10.17487/RFC1122, October 1989,
	<https://www.rfc-editor.org/info/rfc1122>.		<https://www.rfc-editor.org/info/rfc1122>.
	skipping to change at page 101, line 8 ¶		skipping to change at page 101, line 8 ¶
	13.2. Informative References		13.2. Informative References
	[I-D.boucadair-dots-earlydata]		[I-D.boucadair-dots-earlydata]
	Boucadair, M. and R. K, "Using Early Data in DOTS", draft-		Boucadair, M. and R. K, "Using Early Data in DOTS", draft-
	boucadair-dots-earlydata-00 (work in progress), January		boucadair-dots-earlydata-00 (work in progress), January
	2019.		2019.
	[I-D.ietf-core-comi]		[I-D.ietf-core-comi]
	Veillette, M., Stok, P., Pelov, A., Bierman, A., and I.		Veillette, M., Stok, P., Pelov, A., Bierman, A., and I.
	Petrov, "CoAP Management Interface", draft-ietf-core-		Petrov, "CoAP Management Interface", draft-ietf-core-
	comi-07 (work in progress), July 2019.		comi-08 (work in progress), September 2019.
	[I-D.ietf-core-yang-cbor]		[I-D.ietf-core-yang-cbor]
	Veillette, M., Petrov, I., and A. Pelov, "CBOR Encoding of		Veillette, M., Petrov, I., and A. Pelov, "CBOR Encoding of
	Data Modeled with YANG", draft-ietf-core-yang-cbor-10		Data Modeled with YANG", draft-ietf-core-yang-cbor-11
	(work in progress), April 2019.		(work in progress), September 2019.
	[I-D.ietf-dots-architecture]		[I-D.ietf-dots-architecture]
	Mortensen, A., K, R., Andreasen, F., Teague, N., and R.		Mortensen, A., K, R., Andreasen, F., Teague, N., and R.
	Compton, "Distributed-Denial-of-Service Open Threat		Compton, "Distributed-Denial-of-Service Open Threat
	Signaling (DOTS) Architecture", draft-ietf-dots-		Signaling (DOTS) Architecture", draft-ietf-dots-
	architecture-14 (work in progress), May 2019.		architecture-14 (work in progress), May 2019.
	[I-D.ietf-dots-data-channel]		[I-D.ietf-dots-data-channel]
	Boucadair, M. and R. K, "Distributed Denial-of-Service		Boucadair, M. and R. K, "Distributed Denial-of-Service
	Open Threat Signaling (DOTS) Data Channel Specification",		Open Threat Signaling (DOTS) Data Channel Specification",
	draft-ietf-dots-data-channel-30 (work in progress), July		draft-ietf-dots-data-channel-31 (work in progress), July
	2019.		2019.
	[I-D.ietf-dots-multihoming]		[I-D.ietf-dots-multihoming]
	Boucadair, M., K, R., and W. Pan, "Multi-homing Deployment		Boucadair, M., K, R., and W. Pan, "Multi-homing Deployment
	Considerations for Distributed-Denial-of-Service Open		Considerations for Distributed-Denial-of-Service Open
	Threat Signaling (DOTS)", draft-ietf-dots-multihoming-02		Threat Signaling (DOTS)", draft-ietf-dots-multihoming-02
	(work in progress), July 2019.		(work in progress), July 2019.
	[I-D.ietf-dots-server-discovery]		[I-D.ietf-dots-server-discovery]
	Boucadair, M. and R. K, "Distributed-Denial-of-Service		Boucadair, M. and R. K, "Distributed-Denial-of-Service
	Open Threat Signaling (DOTS) Server Discovery", draft-		Open Threat Signaling (DOTS) Agent Discovery", draft-ietf-
	ietf-dots-server-discovery-04 (work in progress), June		dots-server-discovery-05 (work in progress), August 2019.
	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., Moskowitz, R., Teague, N., Xia,
	Teague, N., Xia, L., and K. Nishizuka, "Use cases for DDoS		L., and K. Nishizuka, "Use cases for DDoS Open Threat
	Open Threat Signaling", draft-ietf-dots-use-cases-18 (work		Signaling", draft-ietf-dots-use-cases-20 (work in
	in progress), July 2019.		progress), September 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-32 (work in progress), July		1.3", draft-ietf-tls-dtls13-32 (work in progress), July
	2019.		2019.
	[IANA.CBOR.Tags]		[IANA.CBOR.Tags]
	IANA, "Concise Binary Object Representation (CBOR) Tags",		IANA, "Concise Binary Object Representation (CBOR) Tags",
	<http://www.iana.org/assignments/cbor-tags/		<http://www.iana.org/assignments/cbor-tags/cbor-
	cbor-tags.xhtml>.		tags.xhtml>.
	[IANA.CoAP.Content-Formats]		[IANA.CoAP.Content-Formats]
	IANA, "CoAP Content-Formats",		IANA, "CoAP Content-Formats",
	<http://www.iana.org/assignments/core-parameters/		<http://www.iana.org/assignments/core-parameters/core-
	core-parameters.xhtml#content-formats>.		parameters.xhtml#content-formats>.
	[IANA.MediaTypes]		[IANA.MediaTypes]
	IANA, "Media Types",		IANA, "Media Types",
	<http://www.iana.org/assignments/media-types>.		<http://www.iana.org/assignments/media-types>.
	[proto_numbers]		[proto_numbers]
	"IANA, "Protocol Numbers"", 2011,		"IANA, "Protocol Numbers"", 2011,
	<http://www.iana.org/assignments/protocol-numbers>.		<http://www.iana.org/assignments/protocol-numbers>.
	[RFC3022] Srisuresh, P. and K. Egevang, "Traditional IP Network		[RFC3022] Srisuresh, P. and K. Egevang, "Traditional IP Network
End of changes. 13 change blocks.
	21 lines changed or deleted		20 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/