Re: [Gen-art] Genart last call review of draft-ietf-sfc-multi-layer-oam-23

[Greg Mirsky <[e-mail]>]

Hi Behcet,
thank you for your review and thoughtful suggestions. I've updated the
draft accordingly. Please find diff and the new working version attached.
Also, several notes below are inlined under the GIM>> tag.

Regards,
Greg

On Mon, May 15, 2023 at 8:41 AM Behcet Sarikaya via Datatracker <
[e-mail]> wrote:

> Reviewer: Behcet Sarikaya
> Review result: Ready with Nits
>
> 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.
>
GIM>> This document is the result of merging three documents (one SFC WG
and two individual drafts). Six authors listed on the front page
contributed to at least two documents. We've tried to manage the situation
fairly and with reason. I hope that is understandable and can be accepted.

>
> 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].
>
GIM>> I updated the text. Please let me know if it reflects your view
correctly.

>
> The draft name contains multi-layer which is not mentioned elsewhere in the
> draft.
>
GIM>> The draft went through several revisions, and that is reflected in
some disconnect between its identifier and scope. I hope that is
acceptable.

>
> draft-ietf-sfc-nsh-tlv -> RFC 9263
>
GIM>> Done, thank you.

>
> draft-ietf-sfc-oam-packet normative reference is in RFC Editor Queue
>
GIM>> Thank you for pointing that out. Will update it accordingly after the
publication.

>
> Behcet
>
>
>