Hi, all
I have read the draft and I think it is ready for the IESG review.
It is helpful to inform additional information.
A confusion in the abstract: should it be "a" homogeneous and
extensible surface
Best Regards
Zongpeng Du
-Original Message-
From: GROW [mailto:g
Hi Chairs & WG,
I have read the draft and think it is ready to move forward.
Best Regards
Yisong
发件人: GROW 代表 Job Snijders
发送时间: 2021年12月2日 23:11
收件人: thomas.g...@swisscom.com
抄送: grow@ietf.org
主题: Re: [GROW] On LC for draft-ietf-grow-bmp-tlv (ends December 1st 2021)
Hi Folks,
Please take 15
Hi, All:
I have read the draft and think it is ready for the IESG review. There are
scenarios that additional information encoded in the potential TLVs for the
two BMP messages are expected, as also that discussed in the mail list.
Best Regards
Aijun Wang
China Telecom
-Original Message---
Dear all
I have reviewed the draft. It is very useful to provide a uniform TLV
mechanism for various BMP messages.
Best Regards
Shuanglong
-Original Message-
From: GROW [mailto:grow-boun...@ietf.org] On Behalf Of Job Snijders
Sent: Thursday, December 2, 2021 11:11 PM
To: thoma
Similar, I have read this and it seems straightforward.
My only question is around the BMP versioning, do we expect
that to extend past 255 at some point?
- Jared
On Mon, Dec 06, 2021 at 06:53:40AM +, matthias.arn...@swisscom.com wrote:
> Hallo GROW WG
>
> I've read
Hi Matthias,
Indeed, adding an ADD-PATH capability TLV to the Route Monitoring message will
be a good use case.
In this way, when the BMP server parses the BGP Update message containing the
ADD-PATH ID, it does not need to check the related Peer Up notification message
again.
BR,
Shunwan
Hi GROW WG,
I have read this draft. I think It is very useful to provide a unified TLV
mechanism for various BMP messages. I support publication of this draft.
Thanks,
Shunwan
-Original Message-
From: GROW [mailto:grow-boun...@ietf.org] On Behalf Of Job Snijders
Sent: Thursday, December
