And as shared John’s concern, the new text looks like fixing the problem
Thank for having updated the document -éric From: iesg <[email protected]> on behalf of John Scudder <[email protected]> Date: Monday, 12 April 2021 at 19:39 To: Donald Eastlake <[email protected]> Cc: Matthew Bocci <[email protected]>, "[email protected]" <[email protected]>, "[email protected]" <[email protected]>, The IESG <[email protected]>, "[email protected]" <[email protected]> Subject: Re: John Scudder's Discuss on draft-ietf-bess-evpn-oam-req-frmwk-08: (with DISCUSS and COMMENT) Thanks for hopping threads, I shoulda caught that last one. Your proposed change looks fine, I’ll remove my DISCUSS in anticipation of you issuing a new version. (One nit on your new text, “in order maximize” should be “in order to maximize”.) —John On Apr 12, 2021, at 1:03 PM, Donald Eastlake <[email protected]<mailto:[email protected]>> wrote: [External Email. Be cautious of content] Hi, On Wed, Apr 7, 2021 at 10:04 PM John Scudder via Datatracker <[email protected]<mailto:[email protected]>> wrote: > > John Scudder has entered the following ballot position for > draft-ietf-bess-evpn-oam-req-frmwk-08: Discuss > > ... > > ---------------------------------------------------------------------- > DISCUSS: > ---------------------------------------------------------------------- > > Section 2.3: > > EVPN Network OAM mechanisms MUST provide in-band monitoring > capabilities. As such, OAM messages MUST be encoded so that they > exhibit identical entropy characteristics to data traffic in order > that they share the same fate. > > It’s not obvious to me what you mean by “identical entropy characteristics to > data traffic”. Surely, different flows may have different entropy > characteristics, so, *which* data traffic? Similarly, with which data traffic > are you saying the OAM messages must share fate? I guess when you changed your COMMENT to a DISCUSS it creates a new thread so I should reply here as I did to this when it was a COMMENT: How about something more like: EVPN Network OAM mechanisms MUST provide in-band monitoring capabilities. OAM messages SHOULD be encoded so that they exhibit similar entropy characteristics to data traffic in order maximize the fate sharing between OAM and data. > ---------------------------------------------------------------------- > COMMENT: > ---------------------------------------------------------------------- > > Thanks for the clear and readable document. I have one nit and one question. > > 1. Section 1, nit: > > “EVPN is an Layer 2” s/an/a/ OK. Thanks, Donald =============================== Donald E. Eastlake 3rd +1-508-333-2270 (cell) 2386 Panoramic Circle, Apopka, FL 32703 USA [email protected]<mailto:[email protected]>
_______________________________________________ BESS mailing list [email protected] https://www.ietf.org/mailman/listinfo/bess
