I am the assigned Gen-ART reviewer for this draft. The General Area
Review Team (Gen-ART) reviews all IETF documents being processed
by the IESG for the IETF Chair.  Please treat these comments just
like any other last call comments.

For more information, please see the FAQ at

<https://wiki.ietf.org/en/group/gen/GenArtFAQ>.

Document: draft-ietf-sfc-multi-layer-oam-??
Reviewer: Behcet Sarikaya
Review Date: 2023-05-15
IETF LC End Date: 2023-05-17
IESG Telechat date: Not scheduled for a telechat

Summary:
This document defines  Service Function Chaining (SFC) Operation, Maintenance and Management (OAM) protocol. It defines in Section 6 ICMP like Echo Request/Reply for SFC to do Operation, Maintenance and Management mainly for Fault Management as SFC messages which constitutes the bulk of SFC OAM protocol. As shepherd write-up explains it grew out of 3 documents all lead by Greg Mirsky when he was with ZTE.
Major issues:

Minor issues:
Author list has 6 people as also indicated in shepherd write-up. The document already contains two names in the contributor list. Strongly recommend having one more in the contributor list.

Nits/editorial comments: please add the and as shown below:
This mechanism enables on-demand Continuity Check and
   Connectivity Verification among other operations over SFC in networks
  and addresses functionalities discussed in Sections 4.1, 4.2, and 4.3 of
   [RFC8924].

The draft name contains multi-layer which is not mentioned elsewhere in the draft.

draft-ietf-sfc-nsh-tlv -> RFC 9263

draft-ietf-sfc-oam-packet normative reference is in RFC Editor Queue


Behcet