[bess] RtgDir review: draft-ietf-bess-evpn-oam-req-frmwk-04.txt

receive, and strive to resolve them through discussion or by updating the draft. Document: draft-ietf-bess-evpn-oam-req-frmwk-04.txt Reviewer: Stig Venaas Review Date: 2021-02-15 IETF LC End Date: 2021-02-16 Intended Status: Informational Summary: This document is basically ready for publication

Re: [bess] WG Last Call, IPR and Implementation poll for draft-ietf-bess-mvpn-msdp-sa-interoperation-03

Hi I support publication of this document, but there are a few minor editorial issues that needs to be addressed. Section 2.1 has minor issues: For comparison, another method of supporting customer ASM is generally referred to "rpt-spt" mode. Section "13. Switching from a

Re: [bess] Call for adoption: draft-zzhang-bess-mvpn-msdp-sa-interoperation-01

Support. Stig On Tue, Mar 20, 2018 at 8:13 AM, Dolganow, Andrew (Nokia - SG/Singapore) wrote: > Support > > Andrew > > Sent from my iPhone > > On Feb 26, 2018, at 8:01 AM, "stephane.litkow...@orange.com" > wrote: > > Hello working

Re: [bess] bess: draft-zzhang-bess-mvpn-msdp-sa-interoperation

Hi On Fri, Nov 24, 2017 at 7:21 AM, Toerless Eckert wrote: > On Fri, Nov 24, 2017 at 02:26:39PM +, Jeffrey (Zhaohui) Zhang wrote: >> > a) I was asking Jeffrey in the WG meeting if he saw any difference >> >between MSDP and 4610 wrt. to the applicability of your draft, and

Re: [bess] WGLC: draft-ietf-bier-mvpn-05

Hi I think this draft is mostly ready. I just have a couple of comments. In section 1: This revision of the document does not specify the procedures necessary to support MVPN customers that are using BIDIR-PIM. Those procedures will be added in a future revision. Remove this text?