Dear all, I've uploaded the below draft for consideration in the RTG WG, outlining a communication semantic for multicast where the endpoint selection is based on a 'common characteristic' in the form of, e.g., a URL, while the path selection is realized through a separate (in the two example source routed) identifier. This links to the discussion in evolving communication semantics during the recent interim meeting where the question on " What are the things that are identified by the identifiers?" was asked.
This draft follows a previously published BIER WG draft but now that the draft aims at including other realizations of the described FRRM communication semantic, I thought that a submission to the RTG WG would make more sense. Any thoughts and feedback are welcome. Best, Dirk -----Original Message----- From: [email protected] [mailto:[email protected]] Sent: 04 July 2022 13:23 To: Dirk Trossen <[email protected]> Subject: New Version Notification for draft-trossen-rtgwg-frrm-00.txt A new version of I-D, draft-trossen-rtgwg-frrm-00.txt has been successfully submitted by Dirk Trossen and posted to the IETF repository. Name: draft-trossen-rtgwg-frrm Revision: 00 Title: Forward Requests Return Multicast (FRRM) Communication Semantic Document date: 2022-07-04 Group: Individual Submission Pages: 17 URL: https://www.ietf.org/archive/id/draft-trossen-rtgwg-frrm-00.txt Status: https://datatracker.ietf.org/doc/draft-trossen-rtgwg-frrm/ Htmlized: https://datatracker.ietf.org/doc/html/draft-trossen-rtgwg-frrm 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. The IETF Secretariat _______________________________________________ rtgwg mailing list [email protected] https://www.ietf.org/mailman/listinfo/rtgwg
