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) | |
|---|---|---|---|
| Last updated | 2019-01-09 (latest revision 2018-10-07) | ||
| Replaced by | draft-ietf-dots-multihoming | ||
| Stream | IETF | ||
| Intended RFC status | (None) | ||
| Formats |
Expired & archived
pdf
htmlized (tools)
htmlized
bibtex
|
||
| Stream | WG state | Adopted by a WG | |
| Document shepherd | No shepherd assigned | ||
| IESG | IESG state | Replaced by draft-ietf-dots-multihoming | |
| Consensus Boilerplate | Unknown | ||
| Telechat date | |||
| Responsible AD | (None) | ||
| Send notices to | (None) | ||
https://www.ietf.org/archive/id/draft-boucadair-dots-multihoming-04.txt
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
(mohamed.boucadair@orange.com)
Tirumaleswar Reddy.K
(tirumaleswarreddy_konda@mcafee.com)
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)