Re: [bess] Opsdir last call review of draft-ietf-bess-bgp-vpls-control-flags-07

Thanks Jouni. Taken care of this feedback in latest version. > -Original Message- > From: Jouni Korhonen via Datatracker [mailto:nore...@ietf.org] > Sent: Sunday, March 31, 2019 1:18 PM > To: ops-...@ietf.org > Cc: i...@ietf.org; draft-ietf-bess-bgp-vpls-control-flags@ietf.org; > bess@

Re: [bess] Benjamin Kaduk's No Objection on draft-ietf-bess-bgp-vpls-control-flags-07: (with COMMENT)

Hi Benjamin Thanks for your detailed feedback. Please see inline for . Regards Ravi > -Original Message- > From: Benjamin Kaduk via Datatracker [mailto:nore...@ietf.org] > Sent: Tuesday, April 9, 2019 8:35 AM > To: The IESG > Cc: draft-ietf-bess-bgp-vpls-control-fl...@ietf.org; Mach Che

Re: [bess] Mirja Kühlewind's No Objection on draft-ietf-bess-bgp-vpls-control-flags-07: (with COMMENT)

Hi Mirja > Given this document updates the normative behaviour of RFC 4761, I would > have expected to see some discussion about interoperability. Is the > behaviour as specified in RFC 4761 not widely deployed/implemented or > would it be possible to add some sentences about interoperability which

Re: [bess] Roman Danyliw's No Objection on draft-ietf-bess-bgp-vpls-control-flags-07: (with COMMENT)

Hi Roman Thanks for your comments. Been addressed in -08. Regards Ravi > -Original Message- > From: Roman Danyliw via Datatracker [mailto:nore...@ietf.org] > Sent: Monday, April 8, 2019 6:33 PM > To: The IESG > Cc: draft-ietf-bess-bgp-vpls-control-fl...@ietf.org; Mach Chen > ; bess-cha..

Re: [bess] Barry Leiba's No Objection on draft-ietf-bess-bgp-vpls-control-flags-07: (with COMMENT)

Hi Barry Thanks for your input. Been addressed in -08. Regards Ravi > -Original Message- > From: Barry Leiba via Datatracker [mailto:nore...@ietf.org] > Sent: Sunday, April 7, 2019 11:02 PM > To: The IESG > Cc: draft-ietf-bess-bgp-vpls-control-fl...@ietf.org; Mach Chen > ; bess@ietf.org

Re: [bess] Éric Vyncke's No Objection on draft-ietf-bess-bgp-vpls-control-flags-07: (with COMMENT)

Thanks Éric. Addressed in -08. > -Original Message- > From: Éric Vyncke via Datatracker [mailto:nore...@ietf.org] > Sent: Saturday, April 6, 2019 2:47 PM > To: The IESG > Cc: draft-ietf-bess-bgp-vpls-control-fl...@ietf.org; Mach Chen > ; bess-cha...@ietf.org; mach.c...@huawei.com; > bess@

Re: [bess] Suresh Krishnan's No Objection on draft-ietf-bess-bgp-vpls-control-flags-07: (with COMMENT)

Hi Suresh I've incorporated your suggestions. Good catch with the PE#. Thanks Ravi > -Original Message- > From: Suresh Krishnan via Datatracker [mailto:nore...@ietf.org] > Sent: Wednesday, April 10, 2019 2:06 PM > To: The IESG > Cc: draft-ietf-bess-bgp-vpls-control-fl...@ietf.org; Mach C

[bess] RtgDir review: draft-ietf-bess-nsh-bgp-control-plane-13

could consider them along with any other IETF Last Call comments that you receive, and strive to resolve them through discussion or by updating the draft. Document: draft-ietf-bess-nsh-bgp-control-plane-13.txt Reviewer: Ravi Singh Review Date: 01-26-2020 Intended Status: Standards Track Summ

[bess] RtgDir Early review: draft-ietf-bess-datacenter-gateway.txt

raft-ietf-bess-datacenter-gateway/>.txt Reviewer: Ravi Singh Review Date: 06/26/2020 Intended Status: Standards track (but is it the right one? Should this be informational instead, since no new encodings are explicitly specified) Summary: I have some minor concerns about this document that I thi

[bess] RtgDir Early review: draft-ietf-bess-datacenter-gateway-10.txt

review can be performed at any time during the draft’s lifetime as a working group document. The purpose of the early review depends on the stage that the document has reached. Document: draft-ietf-bess-datacenter-gateway-10.txt Reviewer: Ravi Singh Review Date: 04/30/2021 Intended Status

[bess] draft-singh-bess-bgp-vpls-control-flags:

Hi This draft clarifies flags processing in the BGP-VPLS specification which was previously unaddressed. https://tools.ietf.org/html/draft-singh-bess-bgp-vpls-control-flags-00 It draft was last presented at IETF-90 @ Toronto (in L2VPN WG). http://www.ietf.org/proceedings/90/slides/slides-90-l2vpn

Re: [bess] Poll for adoption: draft-singh-bess-bgp-vpls-control-flags

[Cced the correct authors' alias] Hi Yes, support (as co-author). The following IPR was disclosed. http://www.ietf.org/mail-archive/web/ipr-announce/current/msg01016.html Regards Ravi > -Original Message- > From: BESS [mailto:bess-boun...@ietf.org] On Behalf Of > thomas.mo...@orange.co

Re: [bess] Poll for adoption: draft-singh-bess-bgp-vpls-control-flags

-homing have some deployments and may run into the issue. Regards Ravi > -Original Message- > From: thomas.mo...@orange.com [mailto:thomas.mo...@orange.com] > Sent: Monday, October 5, 2015 12:29 AM > To: bess@ietf.org; draft-singh-bess-bgp-vpls-control-fl...@tools.ietf.o

[bess] RtgDir review: draft-ietf-bess-evpn-etree-12

comments that you receive, and strive to resolve them through discussion or by updating the draft. Document: draft-ietf-bess-evpn-etree-12 Reviewer: Ravi Singh Review Date: 08/15/2017 Intended Status: Standards track Summary: I have some concerns about this document that I think should be resolved

Re: [bess] WG Last Call and IPR Poll for draft-ietf-bess-bgp-vpls-control-flags-04

Hi >If you are listed as an author or a contributor of this document, please >respond to this email and indicate whether or not you are aware of any >relevant undisclosed IPR, copying the BESS >mailing list. The document won't >progress without answers from all the authors and contributors. Not

[bess] Rtgdir last call review of draft-ietf-bess-evpn-proxy-arp-nd-09

Reviewer: Ravi Singh Review result: Has Nits Hello, I have been selected as the Routing Directorate reviewer for this draft. The Routing Directorate seeks to review all routing or routing-related drafts as they pass through IETF last call and IESG review, and sometimes on special request. The