Multi-homing Deployment Considerations for Distributed-Denial-of-Service Open Threat Signaling (DOTS)
draft-boucadair-dots-multihoming-04
Document | Type |
Replaced Internet-Draft
(dots WG)
Expired & archived
|
|
---|---|---|---|
Authors | Mohamed Boucadair , Tirumaleswar Reddy.K | ||
Last updated | 2019-01-09 (Latest revision 2018-10-07) | ||
Replaced by | draft-ietf-dots-multihoming | ||
RFC stream | Internet Engineering Task Force (IETF) | ||
Intended RFC status | (None) | ||
Formats | |||
Additional resources | Mailing list discussion | ||
Stream | WG state | Adopted by a WG | |
Document shepherd | (None) | ||
IESG | IESG state | Replaced by draft-ietf-dots-multihoming | |
Consensus boilerplate | Unknown | ||
Telechat date | (None) | ||
Responsible AD | (None) | ||
Send notices to | (None) |
This Internet-Draft is no longer active. A copy of the expired Internet-Draft is available in these formats:
Abstract
This document discusses multi-homing considerations for Distributed- Denial-of-Service Open Threat Signaling (DOTS). The goal is to provide a set of guidance for DOTS clients/gateways when multihomed.
Authors
Mohamed Boucadair
Tirumaleswar Reddy.K
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)