Realizing Forward Requests Return Multicast Semantic with BIER
draft-trossen-bier-frrm-00
| Document | Type |
Replaced Internet-Draft
(individual)
Expired & archived
|
|
|---|---|---|---|
| Author | Dirk Trossen | ||
| Last updated | 2022-02-21 | ||
| Replaced by | draft-trossen-rtgwg-frrm | ||
| RFC stream | (None) | ||
| Intended RFC status | (None) | ||
| Formats | |||
| Stream | Stream state | (No stream defined) | |
| Consensus boilerplate | Unknown | ||
| RFC Editor Note | (None) | ||
| IESG | IESG state | Replaced by draft-trossen-rtgwg-frrm | |
| 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 introduces a semantic for multicast that is based on initiating forward requests, resulting in dynamic return multicast to the set of initiating clients. The key dynamic nature here is represented in the return multicast being possibly different for every transmission. We introduce this semantic more formally, present exemplifying use cases and then focus on realizing this semantic using BIER technology. Although this document formally introduces the FRRM semantic as a new communication semantic, it does not intend to show the realization of it through any other means besides BIER. This is left for separate documents, if desired.
Authors
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)