Hi Acee, Thanks for the suggestion. The name ""Flex Algorithm Traffic Class (FATC)" looks acceptable to me.
However, whatever name I/We pick, there would be disagreement. That is normal. Before a better name is finalized, we could call it nickname “Pizza” if the term, VFA, is not considered comfortable to some of you. We can use these terms interchangeably. And we will make some change in later draft. The base Algo could be 128-255 or 0. Algo 0 is not included in the -02 draft. With the inclusion of Algo 0, there could be some impact to the re-naming of the term. Rgds Louis -----Original Message----- From: Acee Lindem <[email protected]> Sent: Saturday, April 8, 2023 2:43 AM To: Louis Chan <[email protected]> Cc: lsr <[email protected]> Subject: Re: IETF-116 LSR - IGP extensions for Advertising Offset for Flex-Algorithm [External Email. Be cautious of content] Hi Louis, In the interest of initiating discussion, I would like to propose the term "Flex Algorithm Traffic Class (FATC)" for the sub-division of flex-algorithm traffic referred to in the draft as “Virtual Flex Algorithm”. Also, in your terminology, you refer referred to TLVs and fields with simply “Algorithm” when RFC 9350 uses “Flex Algorithm”. Thanks, Acee Juniper Business Use Only _______________________________________________ Lsr mailing list [email protected] https://www.ietf.org/mailman/listinfo/lsr
