Hi WG,
We had good support on this document, the document is adopted as a WG doc.
Authors,
Please publish the doc as -ietf-
Thanks,
From: Satya Mohanty (satyamoh)
Sent: vendredi 23 avril 2021 23:48
To: slitkows.i...@gmail.com; bess@ietf.org
Cc: bess-cha...@ietf.org
Hi Jeffrey, all,
First of all, I am not against the process of this draft.
What I really want to discuss is about the "right" design of BIER service
solution to make it really implementable and deployable, before it goes to a
wrong direction IMO.
The first design of BIER is based on MPLS, and
Hi Sergey,
Thanks for the comments. We would like to avoid adding another code point
within the value field, as every new encoding of the "weight" will require
a new code point. Agree that we should specify the default units (for which
the consensus on the thread appears to be Mbps), but would
Hi Muthu,
(Speaking as co-chair)
Thanks for the feedback on the intended status. This has to be clarified
however this is not a blocking point for the adoption. We have time to figure
out the intended status of the document with the authors/WG and adjust the text
accordingly.
A New Internet-Draft is available from the on-line Internet-Drafts directories.
This draft is a work item of the BGP Enabled ServiceS WG of the IETF.
Title : Weighted Multi-Path Procedures for EVPN Multi-Homing
Authors : Neeraj Malhotra
Hi Sergey, Bruno,
Many thanks for the detailed review and comments. Discussed with co-authors
and have enhanced the 'value' encoding to explicitly encode weight units as
default or generalized as suggested below. I have published a revision that
incorporates all comments discussed on this thread,
Hi Jeffrey
I read the draft and saw your comments that RFC 6514 mentions MSDP on the
PE.
In what use case would SP have to run Anycast RP / MSDP on the PE when that
ASM control plane function can all be done on the CE.
I guess there maybe customers looking for value added service to have the
SP
Hi Neeraj,thank you for the feedback. I agree that allocating a new code point for every possible calculation method would be cumbersome.How about a middle ground solution, with allocation of just a few values (even 2 would suffice: 1 for BW in whatever units we decide; the other "catch-all"