Dynamic-Anycast (Dyncast) Requirements
draft-liu-dyncast-reqs-00
| Document | Type |
This is an older version of an Internet-Draft whose latest revision state is "Replaced".
Expired & archived
|
|
|---|---|---|---|
| Authors | Peng Liu , Peter Willis , Dirk Trossen | ||
| Last updated | 2021-08-19 (Latest revision 2021-02-15) | ||
| Replaced by | draft-liu-dyncast-gap-reqs | ||
| RFC stream | (None) | ||
| Formats | |||
| Stream | Stream state | (No stream defined) | |
| Consensus boilerplate | Unknown | ||
| RFC Editor Note | (None) | ||
| IESG | IESG state | Expired | |
| 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 draft provides requirements for an architecture addressing the problems outlined in the use case and problem statement draft for Dyncast [DYNCAST-PS].
Authors
Peng Liu
Peter Willis
Dirk Trossen
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)