Forward Requests Return Multicast (FRRM) Communication Semantic
draft-trossen-rtgwg-frrm-00
| Document | Type |
Expired Internet-Draft
(individual)
Expired & archived
|
|
|---|---|---|---|
| Author | Dirk Trossen | ||
| Last updated | 2023-01-05 (Latest revision 2022-07-04) | ||
| Replaces | draft-trossen-bier-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 | 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 document introduces a communication semantic for multicast that is initiated through forward requests, resulting in dynamic return multicast to the set of initiating clients. The key dynamic nature here is the return multicast relations being possibly different for every transmission. We introduce this semantic more formally, present exemplifying use cases and then focus on realizing this semantic using two multicast technologies. Although this document formally introduces the FRRM semantic as a new communication semantic, it does not intend to show the realization of it through the specific multicast technologies in all details. 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.)