Re: [sfc] Regarding last call for draft-ietf-sfc-multi-layer-oam

Greg Mirsky <gregimirsky@gmail.com> Tue, 23 November 2021 21:05 UTC

Return-Path: <gregimirsky@gmail.com>
X-Original-To: sfc@ietfa.amsl.com
Delivered-To: sfc@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 182D23A0799 for <sfc@ietfa.amsl.com>; Tue, 23 Nov 2021 13:05:32 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.097
X-Spam-Level:
X-Spam-Status: No, score=-2.097 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id fg1vcvSvT35i for <sfc@ietfa.amsl.com>; Tue, 23 Nov 2021 13:05:27 -0800 (PST)
Received: from mail-ed1-x52d.google.com (mail-ed1-x52d.google.com [IPv6:2a00:1450:4864:20::52d]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 462683A0793 for <sfc@ietf.org>; Tue, 23 Nov 2021 13:05:27 -0800 (PST)
Received: by mail-ed1-x52d.google.com with SMTP id z5so674443edd.3 for <sfc@ietf.org>; Tue, 23 Nov 2021 13:05:27 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20210112; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=MxMHbB+cy+yRJNTXI+IJQ56gYn6CNI4Pme4YNjHRsDg=; b=HbG39gLXOgPRQ2CrCSidYb+Ta832ReXX5KSvg8K0q5iliPS+HvL3eSaWuBPZrUj3zM gA0nHxJ5Eb/GXdwgSbDFx9VWWkPY/B1/2K2gR3q2XZHFpi/FHlErqiWpkkSECOfYGsCP +33jEEMePWbXiv+hz8WI5r0PqvVJwnzBCDW1Knc+xO0U4NfI651q3lesQPI4hXcK5j3C fmDdzGnwpnqiKnJfM8EDN2LCCpJ+W4j0PPp8HiCWUmiuWNABBqFoD3m7uCJ197W3AmFA BOdFUBmK/NAbBsLWlWWRV627teo3HFXrGi2tLX/GWdGojBGP5XtjfvsUCs/ir2V7jKTz nqiQ==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=MxMHbB+cy+yRJNTXI+IJQ56gYn6CNI4Pme4YNjHRsDg=; b=S1P5gAOi8kWlP1nrs7r8gexbR9ycoQlO/TPTRwo2issn+swnnHCcVgpBkEOpYge4x5 rKzwaHaWGT2dhUqZxAj4a1Cc1sgAAayTRtMzQYpyUBo6qXywUnyLjEBJDsGl5l7fLjNT 6S5bur8cBDvFRsoOrXHf7X3JSCyRCKzgSBFnyE5d9xrHHzzob8WISViYkwmFevTy831D xVCatY2X7frWtqSFRW/gQTbc6fKbmMDKc7GOK2ddDonRz8T6+RAfL/L+D85zPlBiWwgy WWPi110ssQY6nSHvCX9Sl1p2hm1jozrEBMDfNrMAqmD/5c1vA+/eNlaGgq+DCEf3vDC/ s8Xg==
X-Gm-Message-State: AOAM533pBCy5BJ9b7Q1lrhPGfcRNtrhEQOGMMk0KMe5DBp/hKV56MbgY oVWwS17LL9KrwbJnppXg7zhxJ1xE7UlsQy7Iinoan9pl3UE=
X-Google-Smtp-Source: ABdhPJzlcORvOk8Vn7IigcW+zjvtdjPuaTSANrMMcaMz8aRcCfbP7iIgd4OSgEyNQgtYGT90HbaMs0DqEFmAFtxuhkY=
X-Received: by 2002:a05:6402:4389:: with SMTP id o9mr14312462edc.138.1637701523841; Tue, 23 Nov 2021 13:05:23 -0800 (PST)
MIME-Version: 1.0
References: <CO1PR13MB4920BAA670BC738A6E52ED9485609@CO1PR13MB4920.namprd13.prod.outlook.com>
In-Reply-To: <CO1PR13MB4920BAA670BC738A6E52ED9485609@CO1PR13MB4920.namprd13.prod.outlook.com>
From: Greg Mirsky <gregimirsky@gmail.com>
Date: Tue, 23 Nov 2021 13:05:12 -0800
Message-ID: <CA+RyBmW=mFPFQQMW0SHE7ihg9iSCBDvcO=R+VVX3jm3gaEprvQ@mail.gmail.com>
To: Linda Dunbar <linda.dunbar@futurewei.com>
Cc: Service Function Chaining IETF list <sfc@ietf.org>, "Joel M. Halpern" <jmh@joelhalpern.com>
Content-Type: multipart/alternative; boundary="00000000000093a6dc05d17b1948"
Archived-At: <https://mailarchive.ietf.org/arch/msg/sfc/9XGmKNx6_I_-AdYoZWRR6lGCx5E>
Subject: Re: [sfc] Regarding last call for draft-ietf-sfc-multi-layer-oam
X-BeenThere: sfc@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Network Service Chaining <sfc.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/sfc>, <mailto:sfc-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/sfc/>
List-Post: <mailto:sfc@ietf.org>
List-Help: <mailto:sfc-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/sfc>, <mailto:sfc-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 23 Nov 2021 21:05:32 -0000

Hi Linda,
thank you for supporting this work and sharing your comments. Please find
my notes in-lined below under the GIM>> tag. I hope the proposed update
addresses your concerns.

Regards,
Greg

On Tue, Nov 23, 2021 at 11:29 AM Linda Dunbar <linda.dunbar@futurewei.com>
wrote:

> I support the WGLC for the draft-ietf-sfc-multi-layer-oam-16
>
>
>
> I have some questions though:
>
>
>
> The Req #1 says that Active SFC OAM should traverse the same path .. in
> the transport layer as the SFC data packet.
>
> Is the “Transport Layer” refers to TCP/QUIC/UDP transport layer? Or
> referring to the underlay network path?
>
GIM>> Thank you for pointing this out. You're right, the terminology is not
accurate and I propose s/transport/underlay network/. (I've noticed one
more place where this update is needed.)

>
>
> Is it necessary for all functions on the SFC to process the Active SFC OAM
> data packets?
>
GIM>> This document is to apply to Classifiers, SFFs. We don't require SF
and SF Proxy to process SFC Active OAM. If we consider an intermediate SFF,
then it is required to process Active SFC OAM packets without passing it to
an SF/SF Proxy.

> The Req#3 says that Egress node must send the “Remote Defect Indication”
> to the ingress node. Is it necessary for the intermediate Functions to send
> “Remote Defect Indication” to the ingress node?
>
GIM>> RDI, as I understand its function, is used in one-way protocols that
detect a failure in the network. An egress node sets RDI in OAM packets
notifying the ingress of a detected defect. I don't see an intermediate
node setting RDI, as it is not detecting a defect in the SFP. RDI is not
useful in FM OAM protocols that use round-trip methods, e.g., ping.

>
>
>
>
> Thank you
>
> Linda Dunbar
>
>
>
>
>
> On Mon, Nov 1, 2021 at 2:50 PM Joel Halpern Direct
>
> <jmh.direct@joelhalpern.com> <&lt;jmh.direct@joelhalpern.com&gt;> wrote:
>
> >
>
> > I have received a polite request with explanation for delay asking for
>
> > more time to read and review the subject document.  Given the state of
>
> > the working group, i want to encourage any and all review.  So I am
>
> > extending the last call by two additional weeks.
>
> >
>
> > Please read and review the document.
>
> > Also, if you are willing to serve as shepherd for this, please let the
>
> > chairs know.  (Don't worry if you have not shepherded a document before.
>
> >   The chairs are more than happy to help you with the process.)
>
> >
>
> > Thank you,
>
> > Joel
>
> >
>
> > _______________________________________________
>
> > sfc mailing list
>
> > sfc@ietf.org
>
> > https://www.ietf.org/mailman/listinfo/sfc
>
>
> _______________________________________________
> sfc mailing list
> sfc@ietf.org
> https://www.ietf.org/mailman/listinfo/sfc
>