Re: [sfc] Fwd: I-D Action: draft-ietf-sfc-multi-layer-oam-16.txt

Gyan Mishra <hayabusagsm@gmail.com> Sat, 20 November 2021 04:01 UTC

Return-Path: <hayabusagsm@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 D59C23A0B0F for <sfc@ietfa.amsl.com>; Fri, 19 Nov 2021 20:01:00 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.087
X-Spam-Level:
X-Spam-Status: No, score=-2.087 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, T_REMOTE_IMAGE=0.01, 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 xl5kG3VPOLtX for <sfc@ietfa.amsl.com>; Fri, 19 Nov 2021 20:00:56 -0800 (PST)
Received: from mail-pg1-x533.google.com (mail-pg1-x533.google.com [IPv6:2607:f8b0:4864:20::533]) (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 30EA73A0AFE for <sfc@ietf.org>; Fri, 19 Nov 2021 20:00:56 -0800 (PST)
Received: by mail-pg1-x533.google.com with SMTP id t4so2968522pgn.9 for <sfc@ietf.org>; Fri, 19 Nov 2021 20:00:56 -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=mFr2bqBMT+MIr9s6+XwEoebfPbPbwEsPAWE4P6LVZ/g=; b=gwVrtCHIBVBSp7tvVJicI69KGFuVp+pydiuioTZeWO1kR1zHiRLmbKabg/0B9RGdxi R5rgmlvjWuBpAnOP7hpgbiCDTekt4HMXCzBFzU1Z1oLn9i86JvIn8UgZ79QKnj1R2crz HNXbBj6a5E6P1gw6D8ESsf9LGMQNus1PkGAi2BEv8c1gJMdi31mXKDwIYleCGelMOKo6 Iz8RRzvzaVofoJzYkTAbmTiwPcjPAXMeDHpSzaI884RhKwPl8GV+mMx3tG89h1ZeCiTV Xg4NAca2e+Cf48mBqmW0DICdtcLuvB0yOIDOzlFVa3uFd1sXdAZsVh1PctmAxaclKo6O qV6Q==
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=mFr2bqBMT+MIr9s6+XwEoebfPbPbwEsPAWE4P6LVZ/g=; b=2ZvaxRaJxZI9RqnnOmVlaF1KtMnuCIDWTQddIvJoZyeieCQZmMK7qvEoF2IotOtp8K wJuLUI2m06pmFKGAB34mej2wfRr/Ca/o6+WQYl0vIzFcoNWG1AOYsesTF4JJPXcTWv2F rzvPg+7wWqFf5trjLRWBPG2XP4SaT9eQQGoB59Xc8NzWOT2Nsr7naAt83Xb2s5sYaV8Z e9fSDNuDk7SKKW4tUc2eaGhJxx0pHRBJYPPoxc0konBfdZmokOGft/vTSjnV9H2KNSk1 qXaEv8zJLAkp8WrVt5RCKGzY3/Ra5xgcDpsPKemivQEI9bphSjku4lHP6yKN6WUOx2XD j7BQ==
X-Gm-Message-State: AOAM532qP0RWtHpa490t4WiRI5BN3oB1shOmzkLwMq2leyfPi4MYoOTn rfDtoWk3ABa5dDGNpayYHWEzt1XnHiL+f3j9LrYrtd8o
X-Google-Smtp-Source: ABdhPJzma9MqX6Q8BA9vwEfMzT7f6QaoqdZpQBuf3et1EyqwJ+3JT1SUDAgzgcUE71kq/KcICLpxc2ECLqtwHD3WwzM=
X-Received: by 2002:a05:6a00:178c:b0:4a2:f71e:36aa with SMTP id s12-20020a056a00178c00b004a2f71e36aamr29993720pfg.68.1637380854310; Fri, 19 Nov 2021 20:00:54 -0800 (PST)
MIME-Version: 1.0
References: <e89dc949-cd19-f63c-a5cd-3b94af2cb4f9@joelhalpern.com> <202111021002181121996@zte.com.cn> <CALW7UnFzuyi9xicCPQ14S+_Y+2RMua8JnyeQ66_T8X4+PosGUA@mail.gmail.com>
In-Reply-To: <CALW7UnFzuyi9xicCPQ14S+_Y+2RMua8JnyeQ66_T8X4+PosGUA@mail.gmail.com>
From: Gyan Mishra <hayabusagsm@gmail.com>
Date: Fri, 19 Nov 2021 23:00:42 -0500
Message-ID: <CABNhwV1xUg9yVSnMWO5brgqf8RSo3wzPW2-b+iuEhagm5bGzhQ@mail.gmail.com>
To: Linda Wang <lindawangjoy@gmail.com>
Cc: Greg Mirsky <gregimirsky@gmail.com>, meng.wei2@zte.com.cn, sfc@ietf.org
Content-Type: multipart/alternative; boundary="0000000000002ee95c05d130702f"
Archived-At: <https://mailarchive.ietf.org/arch/msg/sfc/444Mae-MF_OPx6gy37U1GBuUXWc>
Subject: Re: [sfc] Fwd: I-D Action: draft-ietf-sfc-multi-layer-oam-16.txt
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: Sat, 20 Nov 2021 04:01:01 -0000

Dear Chairs & All

As co-author I support publication of this draft.

This specification fills a crucial gap for operators for new OAM
functionality, with an Active Multi layer OAM model, by defining
extensibility with Active OAM messages, in NSH,  to troubleshoot faults in
the data plane SFC forwarding plane, SFP E2E path in the service plane
framework.

Kind Regards

Gyan
Verizon

On Wed, Nov 10, 2021 at 9:56 PM Linda Wang <lindawangjoy@gmail.com> wrote:

> Dear Chairs & all,
>
> I support the publication of this draft, and I am not aware of any
> undisclosed IPR.
>
> Thanks so much:)
>
> BRs,
> Linda
>
> On Tue, Nov 2, 2021 at 1:02 PM <meng.wei2@zte.com.cn> wrote:
>
>> Dear SFC Chairs & all,
>>
>> I support the publication of this draft. I am not aware of any
>> undisclosed IPR.
>>
>>
>> Best Regards,
>>
>> Wei Meng
>>
>> Director of Standard and Open Source Planning
>>
>> Technology Planning Dept./System Product
>>
>>
>>
>> *ZTE Corporation*
>>
>> NO 50, Ruanjian AVE, Nanjing, P.R.China, 210012
>> <https://www.google.com/maps/search/NO+50,+Ruanjian+AVE,+Nanjing,+P.R.China,+210012?entry=gmail&source=g>
>>
>> T: +86 25 88014635 M: +86 13584013108 <+86%2013584013108>
>>
>> E: meng.wei2@zte.com.cn
>>
>> www.zte.com.cn
>> 原始邮件
>> *发件人:*JoelM.Halpern
>> *收件人:*Greg Mirsky;Service Function Chaining IETF list;
>> *日 期 :*2021年10月20日 02:03
>> *主 题 :**Re: [sfc] Fwd: I-D Action: draft-ietf-sfc-multi-layer-oam-16.txt*
>> While we are conducting the last call, and deciding who will shepherd
>> this document...
>> 1) If anyone would like to shepherd it, please let me or Jim know.
>> 2) Would the authors and key contributors please confirm to the lsit
>> that all known relevant IPR has been disclosed.
>>
>> Thank you,
>> Joel
>>
>> On 10/19/2021 12:39 PM, Greg Mirsky wrote:
>> > Dear Jim and Joel,
>> > we've completed merging the substantive parts of two SFC OAM drafts.
>> > Many thanks to Med for his thorough reviews, thoughtful comments that
>> > helped us improve the document. The authors believe that the draft is
>> > stable and is ready for the WG LC. We greatly appreciate your
>> > consideration of starting the WG LC and are committed to addressing
>> > questions and comments.
>> >
>> > Regards,
>> > Greg (on behalf off the authors)
>> >
>> > ---------- Forwarded message ---------
>> > From: <internet-drafts@ietf.org <mailto:internet-drafts@ietf.org>>
>> > Date: Tue, Oct 19, 2021 at 9:33 AM
>> > Subject: [sfc] I-D Action: draft-ietf-sfc-multi-layer-oam-16.txt
>> > To: <i-d-announce@ietf.org <mailto:i-d-announce@ietf.org>>
>> > Cc: <sfc@ietf.org <mailto:sfc@ietf.org>>
>> >
>> >
>> >
>> > A New Internet-Draft is available from the on-line Internet-Drafts
>> > directories.
>>
>> > This draft is a work item of the Service Function Chaining WG of the IETF.
>> >
>> >          Title           : Active OAM for Service Function Chaining
>> >          Authors         : Greg Mirsky
>> >                            Wei Meng
>> >                            Ting Ao
>> >                            Kent Leung
>> >                            Gyan Mishra
>> >          Filename        : draft-ietf-sfc-multi-layer-oam-16.txt
>> >          Pages           : 37
>> >          Date            : 2021-10-19
>> >
>> > Abstract:
>> >     A set of requirements for active Operation, Administration, and
>> >     Maintenance (OAM) of Service Function Chains (SFCs) in a network is
>> >     presented in this document.  Based on these requirements, an
>>
>> >     encapsulation of active OAM messages in SFC and a mechanism to detect
>> >     and localize defects are described.
>> >
>> >     This document updates RFC 8300.  Particularly, it updates the
>> >     definition of O (OAM) bit in the Network Service Header (NSH) (RFC
>>
>> >     8300) and defines how an active OAM message is identified in the NSH.
>> >
>> >
>> > The IETF datatracker status page for this draft is:
>> > https://datatracker.ietf.org/doc/draft-ietf-sfc-multi-layer-oam/
>> > <https://datatracker.ietf.org/doc/draft-ietf-sfc-multi-layer-oam/>
>> >
>> > There is also an HTML version available at:
>> > https://www.ietf.org/archive/id/draft-ietf-sfc-multi-layer-oam-16.html
>> > <https://www.ietf.org/archive/id/draft-ietf-sfc-multi-layer-oam-16.html
>> >
>> >
>> > A diff from the previous version is available at:
>> > https://www.ietf.org/rfcdiff?url2=draft-ietf-sfc-multi-layer-oam-16
>> > <https://www.ietf.org/rfcdiff?url2=draft-ietf-sfc-multi-layer-oam-16>
>> >
>> >
>> > Internet-Drafts are also available by anonymous FTP at:
>> > ftp://ftp.ietf.org/internet-drafts/ <
>> ftp://ftp.ietf.org/internet-drafts/>
>> >
>> >
>> > _______________________________________________
>> > sfc mailing list
>> > sfc@ietf.org <mailto:sfc@ietf.org>
>> > https://www.ietf.org/mailman/listinfo/sfc
>> > <https://www.ietf.org/mailman/listinfo/sfc>
>>
>> _______________________________________________
>> 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
>>
> _______________________________________________
> sfc mailing list
> sfc@ietf.org
> https://www.ietf.org/mailman/listinfo/sfc
>
-- 

<http://www.verizon.com/>

*Gyan Mishra*

*Network Solutions A**rchitect *

*Email gyan.s.mishra@verizon.com <gyan.s.mishra@verizon.com>*



*M 301 502-1347*