Re: [Bier] Pls "vote" on name (draft-ietf-bier-te-arch)

Toerless, all,

May I add to the mix (which might not help) with the proposal for 'path-based routing' (or BIER-PBR) or 'path-based steering' (or BIER-PST)? If you want to keep a two letter acronym, I'd add 'path steering' (rather than path engineering) to the mix. From the below, without considering any alternatives, I'd go for BIER-PE but it comes with the issues like many two letter acronyms, namely the higher 'collision rate' with others.

Best,

Dirk

-----Original Message-----
From: BIER [mailto:bier-bounces@ietf.org] On Behalf Of Toerless Eckert
Sent: 27 February 2020 21:41
To: bier@ietf.org
Cc: Lou Berger <lberger@labn.net>; bier-ads@ietf.org; BRUNGARD, DEBORAH A <db3546@att.com>; bier-chairs@ietf.org
Subject: [Bier] Pls "vote" on name (draft-ietf-bier-te-arch)

Dear WG

Please chime in with opinions about the following or any new name you like as the new name for BIER-TE. Timeout is deadline for submission of draft before IETF107, when i'll post an update. If you propose a new name try to avoid re-using abbreviations that may be misinterpreted.

5 = best name ever, ... 1 = lame name, no number assigned means 0 votes are just added up and maximum sum option wins.
Explanations if you haven't followed thread at the end.

BIER-PE  - Path Engineering
BIER-ET  - Explicit Trees
BIER-EET - Explicit Engineered Trees
BIER-BET - Bit Engineered Trees
BIER-BST - Bit Steered Trees
BIER-TrE - Tree engineering
BIER-ET  - Engineered Trees
BIER-ST  - Steered Trees

BIER-ASB - Adjacency Steering Bits   (adjacencies are how bits in BIER-PE are defined)
BIER-AB  - Adjacency Bits
BIER-SB  - Steering Bits             (overloads with "Source Block" - never heard)

Thanks,
    Toerless

Explanations: If you have read through the threads with Lou and Deborah, and my understanding is correct:

Lou desired there to be a new name so BIER-TE the forwarding/steering mechanism (this document) is named differently from BIER-TE the larger framework utilizing TEAS/PCE definition (separate future draft).

Lou did not like my "Path Engineering" proposal as the name in the last version of the doc and felt we should pick a name with Steering/routing-policy in it. I think usn only steering/routing would be misleading (confused with unicast approaches).

Deborah pointed to avoiding confusions in the name with pre-established named (e.g.: "PE" meaning Provider Edge).
Said we should finalize on the name before we as the WG should pass the document to IESG. And she asked chairs to extend last-call by one more week (unrelated). Hence timeout end of next week.

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