[Bier] FW: New Version Notification for draft-trossen-bier-frrm-00.txt

Dirk Trossen <dirk.trossen@huawei.com> Mon, 21 February 2022 12:50 UTC

Return-Path: <dirk.trossen@huawei.com>
X-Original-To: bier@ietfa.amsl.com
Delivered-To: bier@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B971C3A103A; Mon, 21 Feb 2022 04:50:22 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.896
X-Spam-Level:
X-Spam-Status: No, score=-1.896 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_BLOCKED=0.001, RCVD_IN_MSPIKE_H4=0.001, RCVD_IN_MSPIKE_WL=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id BSVZfRyG7JsB; Mon, 21 Feb 2022 04:50:18 -0800 (PST)
Received: from frasgout.his.huawei.com (frasgout.his.huawei.com [185.176.79.56]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 4CB373A1037; Mon, 21 Feb 2022 04:50:18 -0800 (PST)
Received: from fraeml711-chm.china.huawei.com (unknown [172.18.147.200]) by frasgout.his.huawei.com (SkyGuard) with ESMTP id 4K2MTn4YFRz6833m; Mon, 21 Feb 2022 20:45:33 +0800 (CST)
Received: from lhreml701-chm.china.huawei.com (10.201.108.50) by fraeml711-chm.china.huawei.com (10.206.15.60) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA256) id 15.1.2308.21; Mon, 21 Feb 2022 13:50:15 +0100
Received: from lhreml701-chm.china.huawei.com (10.201.108.50) by lhreml701-chm.china.huawei.com (10.201.108.50) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA256_P256) id 15.1.2308.21; Mon, 21 Feb 2022 12:50:14 +0000
Received: from lhreml701-chm.china.huawei.com ([10.201.68.196]) by lhreml701-chm.china.huawei.com ([10.201.68.196]) with mapi id 15.01.2308.021; Mon, 21 Feb 2022 12:50:14 +0000
From: Dirk Trossen <dirk.trossen@huawei.com>
To: BIER WG <bier@ietf.org>
CC: "mboned@ietf.org" <mboned@ietf.org>
Thread-Topic: New Version Notification for draft-trossen-bier-frrm-00.txt
Thread-Index: AQHYJx/vthVjxu4DrE6VFzDbEFrqT6yd8bLA
Date: Mon, 21 Feb 2022 12:50:14 +0000
Message-ID: <23a829a6c9d44269a9455c91e6a91f59@huawei.com>
References: <164544709752.14489.13642889531892772536@ietfa.amsl.com>
In-Reply-To: <164544709752.14489.13642889531892772536@ietfa.amsl.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [10.81.211.13]
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-CFilter-Loop: Reflected
Archived-At: <https://mailarchive.ietf.org/arch/msg/bier/aFoXDnGjYBUiscaUxN0m7P_Y5_4>
Subject: [Bier] FW: New Version Notification for draft-trossen-bier-frrm-00.txt
X-BeenThere: bier@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "\"Bit Indexed Explicit Replication discussion list\"" <bier.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/bier>, <mailto:bier-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/bier/>
List-Post: <mailto:bier@ietf.org>
List-Help: <mailto:bier-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/bier>, <mailto:bier-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 21 Feb 2022 12:50:23 -0000

Dear all,

I've posted the below draft as a continuation of the efforts that went originally into the draft https://www.ietf.org/archive/id/draft-ietf-bier-multicast-http-response-06.txt. 

The latter draft had originally gone into WGLC and stirred very good discussions recently based on comments from Sandy, Jake, Gyan, Toerless, among others. However, in discussions with the co-authors of this draft, it became clear that this draft would not be pursued by the co-authors. 

Personally from my side, the focus on HTTP (as an application protocol) lowered my interest in pursuing the original draft. As a consequence, I made an attempt to generalize the previous draft around the underlying multicast communication semantic with the intention to allow for its usage beyond just HTTP. The result is the draft below. 

I would hope that this new draft will attract the interest of the wider community, including those who commented on the original HTTP-centric draft, which is why I include the mboned list in this announcement. If you have any interest to work with me on this draft, please drop me an email (and/or indicate on the list for others to see this wider interest). With this, I'd hope we could pursue this topic further and with wider applicability. 

Best,

Dirk

-----Original Message-----
From: internet-drafts@ietf.org [mailto:internet-drafts@ietf.org] 
Sent: 21 February 2022 13:38
To: Dirk Trossen <dirk.trossen@huawei.com>
Subject: New Version Notification for draft-trossen-bier-frrm-00.txt


A new version of I-D, draft-trossen-bier-frrm-00.txt has been successfully submitted by Dirk Trossen and posted to the IETF repository.

Name:		draft-trossen-bier-frrm
Revision:	00
Title:		Realizing Forward Requests Return Multicast Semantic with BIER
Document date:	2022-02-21
Group:		Individual Submission
Pages:		16
URL:            https://www.ietf.org/archive/id/draft-trossen-bier-frrm-00.txt
Status:         https://datatracker.ietf.org/doc/draft-trossen-bier-frrm/
Htmlized:       https://datatracker.ietf.org/doc/html/draft-trossen-bier-frrm


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.

                                                                                  


The IETF Secretariat