Hi Matthew Will do.
Thanks Parag From: "Bocci, Matthew (Nokia - GB)" <[email protected]> Date: Wednesday, February 2, 2022 at 11:10 AM To: "[email protected]" <[email protected]> Cc: "[email protected]" <[email protected]>, "[email protected]" <[email protected]> Subject: Re: ID-Nits for draft-ietf-bess-evpn-lsp-ping Resent-From: <[email protected]> Resent-To: <[email protected]>, <[email protected]>, <[email protected]>, <[email protected]>, <[email protected]> Resent-Date: Wednesday, February 2, 2022 at 11:09 AM Hi Authors While going through this I have a couple of other comments: Please can you clean up the use of RFC2119 language, in particular capitalizing SHOULD, MUST etc where appropriate. For example, I think the following in Section 4.3 should be corrected: Ethernet Tag field value in EVPN Ethernet AD Sub-TLV, should be set according to the context: o For per-ES context, the Ethernet Tag field in the sub-TLV must be set to the reserved MAX-ET value [RFC7432<https://datatracker.ietf.org/doc/html/rfc7432>] o For per-EVI context, the Ethernet Tag field in the sub-TLV must be set to the non-reserved value Thanks Matthew From: Bocci, Matthew (Nokia - GB) <[email protected]> Date: Wednesday, 2 February 2022 at 16:00 To: [email protected] <[email protected]> Cc: [email protected] <[email protected]> Subject: ID-Nits for draft-ietf-bess-evpn-lsp-ping Hi Authors I am finally doing the document shepherds write up for this draft. ID Nits throws up a few warnings, which I would appreciate if you could fix now before I request publication: https://www.ietf.org/tools/idnits?url=https://www.ietf.org/archive/id/draft-ietf-bess-evpn-lsp-ping-06.txt Thanks Matthew
_______________________________________________ BESS mailing list [email protected] https://www.ietf.org/mailman/listinfo/bess
