Re: [Bier] New Version Notification for draft-trossen-rtgwg-frrm-00.txt

Hi Dirk,

I think this is interesting work and may lead to significant savings in 
appropriate use cases. Its alignment with BIER is not trivial but 
desirable from my perspective.

Kind regards

Michael

Am 12.09.2022 um 09:26 schrieb Dirk Trossen:
> Dear all,
> 
> If anybody is still interested in the ad-hoc multicast capability that was originally described in the WG adopted draft https://datatracker.ietf.org/doc/draft-ietf-bier-multicast-http-response/ and is now extended into a more general draft introducing the FRRM communication semantic https://datatracker.ietf.org/doc/draft-trossen-rtgwg-frrm/, please drop me an email (or respond to the list) for possible ways forward, possible contributions etc.
> 
> Best,
> 
> Dirk
> 
> -----Original Message-----
> From: BIER <bier-bounces@ietf.org> On Behalf Of Dirk Trossen
> Sent: 18 July 2022 09:49
> To: bier@ietf.org
> Subject: [Bier] FW: New Version Notification for draft-trossen-rtgwg-frrm-00.txt
> 
> Dear Bier community,
> 
> I've posted an update to the FRRM draft, previously positioned towards the BIER WG, to the RTG WG, now including a placeholder for MSR6 as another possible realization of this communication semantic. Mostly, I am seeking input from the wider community, including the BIER WG, on how to move this work forward, what WGs may be appropriate (e.g., for solution work but also work on the communication semantic itself).
> 
> Please let me know of any insights and comments you may have, either here or on the RTG WG list.
> 
> Best,
> 
> Dirk
> 
> -----Original Message-----
> From: rtgwg [mailto:rtgwg-bounces@ietf.org] On Behalf Of Dirk Trossen
> Sent: 04 July 2022 15:44
> To: RTGWG <rtgwg@ietf.org>
> Subject: FW: New Version Notification for draft-trossen-rtgwg-frrm-00.txt
> 
> 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: internet-drafts@ietf.org [mailto:internet-drafts@ietf.org]
> Sent: 04 July 2022 13:23
> To: Dirk Trossen <dirk.trossen@huawei.com>
> 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
> rtgwg@ietf.org
> https://www.ietf.org/mailman/listinfo/rtgwg
> 
> _______________________________________________
> BIER mailing list
> BIER@ietf.org
> https://www.ietf.org/mailman/listinfo/bier
> 
> _______________________________________________
> BIER mailing list
> BIER@ietf.org
> https://www.ietf.org/mailman/listinfo/bier

-- 
Prof. Dr. habil. Michael Menth
University of Tuebingen
Faculty of Science
Department of Computer Science
Chair of Communication Networks
Sand 13, 72076 Tuebingen, Germany
phone: (+49)-7071/29-70505
fax: (+49)-7071/29-5220
mailto:menth@uni-tuebingen.de
http://kn.inf.uni-tuebingen.de