Re: [bess] New draft "draft-hr-spring-intentaware-routing-using-color"

2022-07-16 Thread Igor Malyushkin
*Accidently unicasted the previous message to Dhananjaya, replying to the group.* Hello Dhananjaya, Can you please clarify some moments in Section 6.2? First, I don't see any sign of Section 5.1.9 (also referred to in Section 6.3.1.7) in the document. Looks like missed. I'm interested in the next

Re: [bess] New draft "draft-hr-spring-intentaware-routing-using-color"

2022-07-18 Thread Igor Malyushkin
uick review. Please see inline (DR##) > > > > *From: *BESS on behalf of Igor Malyushkin < > gmalyush...@gmail.com> > *Date: *Sunday, July 17, 2022 at 2:50 AM > *To: *"Dhananjaya Rao (dhrao)" > *Cc: *"bess@ietf.org" > *Subject: *Re: [bess

[bess] draft-malyushkin-bess-ip-vpn-abstract-next-hops for WG review

2022-08-23 Thread Igor Malyushkin
Hi all, Recently I posted a draft about a problem I've encountered as an ISP engineer. It is related to IP VPN convergence and especially is applicable to multihomed CEs. I think the solution can be useful for many types of IP VPN deployments, but one of the main drivers for me was the Internet in

Re: [bess] draft-malyushkin-bess-ip-vpn-abstract-next-hops for WG review

2022-08-24 Thread Igor Malyushkin
Hi Linda, Thanks for your comments! I'm glad to know that described problem is under discussion and is also addressed in your solution. I will follow the development of your draft and hope it will be implemented soon. The only thing that concerns me is that the solution described in this document

Re: [bess] draft-malyushkin-bess-ip-vpn-abstract-next-hops for WG review

2022-08-24 Thread Igor Malyushkin
rmational. > [IM] The reason is simple, I thought that any changes that a document can introduce to a running code cannot be described in Informational documents. I will fix it, thanks! > Many thx, > Robert. > > > On Tue, Aug 23, 2022 at 3:45 PM Igor Malyushkin > wrote: >

Re: [bess] draft-malyushkin-bess-ip-vpn-abstract-next-hops for WG review

2022-08-25 Thread Igor Malyushkin
Hi Robert, Thanks for the comments, my inline is below. ср, 24 авг. 2022 г. в 22:46, Robert Raszuk : > Hey Igor, > > >> [IM] Agree. I understood it well before I started drafting. My goal was >> as less as possible touch to VPN and other mechanics. BGP NH tracking >> allows us to implement chang

Re: [bess] Question regarding section 17.3 draft-ietf-bess-rfc7432bis

2023-01-09 Thread Igor Malyushkin
Hi folks, I concur with Sasha. The idea behind retaining locally learned MACs until their timers hit zero is to reduce unknown unicast flooding in a service. All ingress PEs will have time to learn new MAC advertisements from the rest PE behind the ES (if they don't have them apriori). This is act

Re: [bess] Question regarding section 17.3 draft-ietf-bess-rfc7432bis

2023-01-10 Thread Igor Malyushkin
uld mean that it would start flooding for these MAC addresses. > > > > Thank you kindly. > > > > Best Regards, > > Menachem > > > > *From: *Igor Malyushkin > *Date: *Monday, 9 January 2023 at 16:51 > *To: *Alexander Vainshtein > *Cc: *Menachem Dodge ,

[bess] Re: Errata on RFC7117 and RFC8584

2025-01-29 Thread Igor Malyushkin
Hi Gian, Section 9.2.2 cannot be applied, it says that explicitly: Usage of leaf A-D routes is described in the "*Inter-AS* Inclusive P-Multicast Tree A-D/Binding" and "Optimizing Multicast Distribution via Selective Trees" sections. The section in question is named "*Intra-AS* Inclusi

[bess] Re: Errata on RFC7117 and RFC8584

2025-01-29 Thread Igor Malyushkin
Gyan, I’m sorry for a mistake with your name. I’ll be more attentive next time! Ср, 29 янв. 2025 г. в 17:04, Igor Malyushkin : > > Hi Gian, > > Section 9.2.2 cannot be applied, it says that explicitly: > >Usage of leaf A-D routes is described in the "*Inter-AS* Inc