Considerations for stateful vs stateless join router in ANIMA bootstrap
draft-richardson-anima-state-for-joinrouter-02
| The information below is for an old version of the document | |||
|---|---|---|---|
| Document | Type | Expired Internet-Draft (individual) | |
| Author | Michael Richardson | ||
| Last updated | 2018-07-29 (latest revision 2018-01-25) | ||
| Stream | (None) | ||
| Intended RFC status | (None) | ||
| Formats |
Expired & archived
pdf
htmlized (tools)
htmlized
bibtex
|
||
| Additional Resources |
|
||
| Stream | Stream state | (No stream defined) | |
| Consensus Boilerplate | Unknown | ||
| RFC Editor Note | (None) | ||
| IESG | IESG state | Expired | |
| Telechat date | |||
| Responsible AD | (None) | ||
| Send notices to | (None) | ||
This Internet-Draft is no longer active. A copy of
the expired Internet-Draft can be found at
https://www.ietf.org/archive/id/draft-richardson-anima-state-for-joinrouter-02.txt
https://www.ietf.org/archive/id/draft-richardson-anima-state-for-joinrouter-02.txt
Abstract
This document explores a number of issues affecting the decision to use a stateful or stateless forwarding mechanism by the join router (aka join assistant) during the bootstrap process for ANIMA.
Authors
Michael Richardson (mcr+ietf@sandelman.ca)
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)