[Bier] FRRM draft update

Dirk Trossen <dirk.trossen@huawei.com> Wed, 08 June 2022 10:07 UTC

Return-Path: <dirk.trossen@huawei.com>
X-Original-To: bier@ietfa.amsl.com
Delivered-To: bier@ietfa.amsl.com
Received: from localhost (localhost []) by ietfa.amsl.com (Postfix) with ESMTP id 4FB30C15BEC8 for <bier@ietfa.amsl.com>; Wed, 8 Jun 2022 03:07:44 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.908
X-Spam-Status: No, score=-1.908 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_BLOCKED=0.001, RCVD_IN_MSPIKE_H2=-0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([]) by localhost (ietfa.amsl.com []) (amavisd-new, port 10024) with ESMTP id 8SpjYBxSkU3L for <bier@ietfa.amsl.com>; Wed, 8 Jun 2022 03:07:43 -0700 (PDT)
Received: from frasgout.his.huawei.com (frasgout.his.huawei.com []) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id DC12EC15BE7E for <bier@ietf.org>; Wed, 8 Jun 2022 03:07:42 -0700 (PDT)
Received: from fraeml737-chm.china.huawei.com (unknown []) by frasgout.his.huawei.com (SkyGuard) with ESMTP id 4LJ2tn1sC7z67mXD for <bier@ietf.org>; Wed, 8 Jun 2022 18:06:25 +0800 (CST)
Received: from lhreml702-chm.china.huawei.com ( by fraeml737-chm.china.huawei.com ( with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA256) id 15.1.2375.24; Wed, 8 Jun 2022 12:07:39 +0200
Received: from lhreml701-chm.china.huawei.com ( by lhreml702-chm.china.huawei.com ( with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA256_P256) id 15.1.2375.24; Wed, 8 Jun 2022 11:07:39 +0100
Received: from lhreml701-chm.china.huawei.com ([]) by lhreml701-chm.china.huawei.com ([]) with mapi id 15.01.2375.024; Wed, 8 Jun 2022 11:07:39 +0100
From: Dirk Trossen <dirk.trossen@huawei.com>
To: "bier@ietf.org" <bier@ietf.org>
Thread-Topic: FRRM draft update
Thread-Index: Adh7H2Jy3uSmAkudQHWDrlGjKh9U2g==
Date: Wed, 08 Jun 2022 10:07:39 +0000
Message-ID: <b29b4b4ad6984fb1b8d7acbcf0e41533@huawei.com>
Accept-Language: en-US
Content-Language: en-US
x-originating-ip: []
Content-Type: multipart/alternative; boundary="_000_b29b4b4ad6984fb1b8d7acbcf0e41533huaweicom_"
MIME-Version: 1.0
X-CFilter-Loop: Reflected
Archived-At: <https://mailarchive.ietf.org/arch/msg/bier/gqbMEomg8XZ56FA4pt8zRHNq6Ts>
Subject: [Bier] FRRM draft update
X-BeenThere: bier@ietf.org
X-Mailman-Version: 2.1.39
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: Wed, 08 Jun 2022 10:07:44 -0000


You may recall a presentation on the Forward request return multicast (FRRM) draft (https://datatracker.ietf.org/doc/html/draft-trossen-bier-frrm-00.html) at IETF113, using BIER as a transport albeit not limited to it.

I was wondering if there is some interest in the community to develop this work further, either specific to BIER or more generally (with discussion on where possibly to place such work).

Please drop me an email or indicate via the list; I can arrange a call among those interested.