IETF Logo Mail Archive

RE: [Bier] [pim] Q on the congestion awareness of routing protocols

Dirk Trossen <dirk.trossen@huawei.com> Tue, 06 December 2022 06:57 UTC

Return-Path: <dirk.trossen@huawei.com>
X-Original-To: tsv-area@ietfa.amsl.com
Delivered-To: tsv-area@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 1B044C14CE34; Mon, 5 Dec 2022 22:57:34 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.327
X-Spam-Level:
X-Spam-Status: No, score=-1.327 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, INVALID_MSGID=0.568, RCVD_IN_DNSWL_BLOCKED=0.001, RCVD_IN_MSPIKE_H2=-0.001, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001, URIBL_DBL_BLOCKED_OPENDNS=0.001, URIBL_ZEN_BLOCKED_OPENDNS=0.001] autolearn=no autolearn_force=no
Received: from mail.ietf.org ([50.223.129.194]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id RTzE73xJYNOY; Mon, 5 Dec 2022 22:57:29 -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 547A9C14CEE4; Mon, 5 Dec 2022 22:57:29 -0800 (PST)
Received: from lhrpeml500001.china.huawei.com (unknown [172.18.147.201]) by frasgout.his.huawei.com (SkyGuard) with ESMTP id 4NRB3t2bRGz6864S; Tue, 6 Dec 2022 14:54:34 +0800 (CST)
Received: from lhrpeml500003.china.huawei.com (7.191.162.67) by lhrpeml500001.china.huawei.com (7.191.163.213) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256) id 15.1.2375.34; Tue, 6 Dec 2022 06:57:27 +0000
Received: from lhrpeml500003.china.huawei.com ([7.191.162.67]) by lhrpeml500003.china.huawei.com ([7.191.162.67]) with mapi id 15.01.2375.034; Tue, 6 Dec 2022 06:57:27 +0000
From: Dirk Trossen <dirk.trossen@huawei.com>
To: Dino Farinacci <farinacci@gmail.com>, Stewart Bryant <stewart.bryant@gmail.com>
CC: Matt Mathis <mattmathis=40google.com@dmarc.ietf.org>, Jon Crowcroft <Jon.Crowcroft@cl.cam.ac.uk>, BIER WG <bier@ietf.org>, tsv-area <tsv-area@ietf.org>, pim <pim@ietf.org>, routing-discussion <routing-discussion@ietf.org>
Subject: RE: [Bier] [pim] Q on the congestion awareness of routing protocols
Thread-Topic: [Bier] [pim] Q on the congestion awareness of routing protocols
Thread-Index: AQHZCOlmAcYH0tJlNEaet8XyonprQK5gbi2D
Date: Tue, 06 Dec 2022 06:57:27 +0000
Message-ID: 6DE3A953-568A-4B7F-A04A-E2276C385E88
References: <CAH56bmBnqi4peTWUXOVy0KRRXRc1L7TP+atFfVF6qb_OKBMBwg@mail.gmail.com> <C303F9BF-F96A-4710-A4B5-4228807C07F7@gmail.com>, <52907137-CA5A-4042-AB2C-23FD9B032210@gmail.com>
In-Reply-To: <52907137-CA5A-4042-AB2C-23FD9B032210@gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
Content-Type: multipart/alternative; boundary="_000_6DE3A953568A4B7FA04AE2276C385E88_"
MIME-Version: 1.0
X-CFilter-Loop: Reflected
Archived-At: <https://mailarchive.ietf.org/arch/msg/tsv-area/uTc1mvTOX3ABxlCOnQ1BpmItHMA>
X-BeenThere: tsv-area@ietf.org
X-Mailman-Version: 2.1.39
Precedence: list
List-Id: IETF Transport and Services Area Mailing List <tsv-area.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/tsv-area>, <mailto:tsv-area-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/tsv-area/>
List-Post: <mailto:tsv-area@ietf.org>
List-Help: <mailto:tsv-area-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tsv-area>, <mailto:tsv-area-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 06 Dec 2022 06:57:34 -0000

Why not doing a series of side meetings and see how it develops? No reason to stick an "operational" name to it, like "shadow RRG" or similar.

Happy to see such side meetings to happen and progress.

Dirk




From:Dino Farinacci <farinacci@gmail.com>
To:Stewart Bryant <stewart.bryant@gmail.com>
Cc:Matt Mathis <mattmathis=40google.com@dmarc.ietf.org>;Jon Crowcroft <Jon.Crowcroft@cl.cam.ac.uk>;BIER WG <bier@ietf.org>;tsv-area <tsv-area@ietf.org>;pim <pim@ietf.org>;routing-discussion <routing-discussion@ietf.org>
Date:2022-12-05 21:37:32
Subject:Re: [Bier] [pim] Q on the congestion awareness of routing protocols

> One thought is that we set up a shadow RRG operating independently of the IETF meeting but meeting concurrently and at the same location. This is what BoFs used to be before the IETF apparatus got hold of them and formalised them. We can still use the draft infrastructure. If we cannot have a IETF list, there is groups.io or similar. All a bit like Internet Routing where we route around damage to the infrastructure.

I'd be all for this idea.

Dino

_______________________________________________
BIER mailing list
BIER@ietf.org
https://www.ietf.org/mailman/listinfo/bier

v2.23.0 | Report a Bug | By Email