I support publishing this document.
However, I have a small concern about it. It seems to recommend that "set
community X" should remove all well-known communities by default. However, the
default removal of certain well-known communities like "NO_EXPORT" by "set
community X" itself surprises man
Acee,
On Mon, Dec 10, 2018 at 10:45:15PM +, Acee Lindem (acee) wrote:
> Just because a piece of information is useful doesn't necessarily mean it
> should be part of the BGP local RIB. In many cases, the BGP process and
> the Global RIB are deaggregated. If we wish to overload BMP with returni
Support. It's a useful document.
BTW, it's useful to collect more default behaviors that vary from vendor to
vendor:
https://tools.ietf.org/id/draft-zhuang-grow-monitoring-bgp-parameters-00.txt
Comments and cooperation are welcome！
Thanks,
Shunwan
-Original Message-
From: GROW [mailto:
Hi Jeff,
On 12/10/18, 5:33 PM, "GROW on behalf of Jeffrey Haas" wrote:
[Note, message reordered and reformatted for quoting clarity]
Tim,
Thank you for your patience for my response.
On Tue, Nov 20, 2018 at 05:42:37AM +, Tim Evens (tievens) wrote:
> On 11
[Note, message reordered and reformatted for quoting clarity]
Tim,
Thank you for your patience for my response.
On Tue, Nov 20, 2018 at 05:42:37AM +, Tim Evens (tievens) wrote:
> On 11/16/18, 1:26 AM, "GROW on behalf of Zhuangshunwan"
> wrote:
> > Jeff Haas said:
> > > I do wish to get thi
Dear all,
So far we only received one note in support of publication. Before
declaring consensus one way or another I'd prefer if we have more
feedback to work with.
Your feedback is crucial to the IETF publication proces, so please
take a few minutes to read the document and consider whether you
