Re: [sfc] Fwd: New Version Notification for draft-ietf-sfc-multi-layer-oam-05.txt

Gyan Mishra <hayabusagsm@gmail.com> Tue, 08 December 2020 01:47 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 47E823A0DA4; Mon, 7 Dec 2020 17:47:28 -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 VA0HfOFkwOPv; Mon, 7 Dec 2020 17:47:26 -0800 (PST)
Received: from mail-pf1-x42d.google.com (mail-pf1-x42d.google.com [IPv6:2607:f8b0:4864:20::42d]) (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 0BB2E3A0DBE; Mon, 7 Dec 2020 17:47:25 -0800 (PST)
Received: by mail-pf1-x42d.google.com with SMTP id 131so12298869pfb.9; Mon, 07 Dec 2020 17:47:25 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=Y2RIhcBgpBCXIZYGHFp4U38qIm6Rwi9VF6qRmMQKA8E=; b=LeE4YrCmmd8X/gk2T29L9FM7ZnH88nySTu1oAROVSmWiw4UFiLOtB3r6smsb/CrWvF JjFu9x8y1qYYKvjfkgzrNq+IygqlWPPOZpRkPCQwHGva8Y8e803vRpx9w9Cr20+3aVkU yFX7BASUSZ85XF5okcrkkw2KLal0g8cZ2zxm0QYz22qcul4+3qWfqXF0wVpHY9UwLNus D5EzLgbUKSP3Xcdr1+n/6E5WrjZxCLY7E+ZLEH2rg+CsURnQhzkLUFNrDYs4C0e8TDAC 3+QqWLaqVgjb7c1x4EavslCoGCx/QRe6PE1zr8QadgyO7k9HuakwbKHMhJixwq/qKRdZ urbg==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=Y2RIhcBgpBCXIZYGHFp4U38qIm6Rwi9VF6qRmMQKA8E=; b=EFVUBTepYEwYOKbrDcGKpzU4YeBimFJusbhdZhVwHqhdtnjMIbSRcRx5OU43sopmVc NbJRB4u7d7p7IivkppXWpEWVHWF0ulGfCFhPzL9dGcHaNiZ6aWkI+c+hzGtiLX4sxzQM Zmp518pXe9THSXahUtjgqj7ciUJyuH0xRVBm/LQYHOhiMhhmZ1VXJtla9bFq8ZlBAn2W bYx9h1Oyt8luRq/w9+O2n/+Aa7n8jSVzi8FD4p+eY4DUkhQDrgHhrnQqJxyVbrnAEHJ7 IZrBmDUriSEPw/3LqO2x6LzKGknDDbCJvlrEqL/RASQg2cwAmmgQfvbl3aGoAlyvYL9r 4l8Q==
X-Gm-Message-State: AOAM533E1pmwWkBiOepO7W5SPNG/4f9+jaQlStFssxkyMT8VnbkllGYz xmMLn6hYnC5t1U8dBC424c9lCjnoPT/RDp5cQUE=
X-Google-Smtp-Source: ABdhPJynwxtKyKswks3BLHXoymQnmY1uDp1drJT0FcEi6d4WPu2FVytPSFxpGSJet8rELsC6uIz4XtzJPn+LHAnxwVg=
X-Received: by 2002:a17:90a:fb97:: with SMTP id cp23mr1651739pjb.215.1607392045253; Mon, 07 Dec 2020 17:47:25 -0800 (PST)
MIME-Version: 1.0
References: <159002475323.18843.9559672930298713998@ietfa.amsl.com> <CA+RyBmXXRoPkhXjhpneC8UyBDbxh8P81YDYpRTnbqQiLu64ogQ@mail.gmail.com>
In-Reply-To: <CA+RyBmXXRoPkhXjhpneC8UyBDbxh8P81YDYpRTnbqQiLu64ogQ@mail.gmail.com>
From: Gyan Mishra <hayabusagsm@gmail.com>
Date: Mon, 07 Dec 2020 20:39:57 -0500
Message-ID: <CABNhwV2MGC8pc8hGZGDK1LSs+dZ54mBOD9t6K=Ci0E95bvxO7w@mail.gmail.com>
To: Greg Mirsky <gregimirsky@gmail.com>
Cc: Service Function Chaining IETF list <sfc@ietf.org>, sfc-chairs@ietf.org
Content-Type: multipart/alternative; boundary="000000000000df487105b5ea1fcc"
Archived-At: <https://mailarchive.ietf.org/arch/msg/sfc/ZxF5I88LPMEUJGSdYHxlwOxwaMY>
Subject: Re: [sfc] Fwd: New Version Notification for draft-ietf-sfc-multi-layer-oam-05.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: Tue, 08 Dec 2020 01:47:35 -0000

Dear Greg & Authors

Please consider adding an improved security mechanism to protect the
integrity of the SFC Echo Request/Reply function.

This feature would be highly valuable to operators.

Thank you

Gyan

On Wed, May 20, 2020 at 10:51 PM Greg Mirsky <gregimirsky@gmail.com> wrote:

> Dear All,
> this version includes a minor update to the Security Considerations
> section.
> We, the authors, believe that the draft is ready for the WG LC. It defines
> an essential function of SFC OAM - SFP Echo request/reply. Per our
> analysis, existing OAM mechanisms cannot support both SFP ping and SFP
> traceroute. Consider ICMP. When encapsulated in NSH, it supports the ping
> function but, per our analysis, cannot be used as an SFP tracing tool.
> We much appreciate your comments and questions.
>
> Dear Jim and Joel,
> please kindly consider the WG LC for this draft.
>
> Regards,
> Greg
>
> ---------- Forwarded message ---------
> From: <internet-drafts@ietf.org>
> Date: Wed, May 20, 2020 at 6:32 PM
> Subject: New Version Notification for draft-ietf-sfc-multi-layer-oam-05.txt
> To: Bhumip Khasnabish <vumip1@gmail.com>, Cui(Linda) Wang <
> lindawangjoy@gmail.com>, Greg Mirsky <gregimirsky@gmail.com>, Wei Meng <
> meng.wei2@zte.com.cn>
>
>
>
> A new version of I-D, draft-ietf-sfc-multi-layer-oam-05.txt
> has been successfully submitted by Greg Mirsky and posted to the
> IETF repository.
>
> Name:           draft-ietf-sfc-multi-layer-oam
> Revision:       05
> Title:          Active OAM for Service Function Chains in Networks
> Document date:  2020-05-20
> Group:          sfc
> Pages:          18
> URL:
> https://www.ietf.org/internet-drafts/draft-ietf-sfc-multi-layer-oam-05.txt
> Status:
> https://datatracker.ietf.org/doc/draft-ietf-sfc-multi-layer-oam/
> Htmlized:
> https://tools.ietf.org/html/draft-ietf-sfc-multi-layer-oam-05
> Htmlized:
> https://datatracker.ietf.org/doc/html/draft-ietf-sfc-multi-layer-oam
> Diff:
> https://www.ietf.org/rfcdiff?url2=draft-ietf-sfc-multi-layer-oam-05
>
> Abstract:
>    A set of requirements for active Operation, Administration and
>    Maintenance (OAM) of Service Function Chains (SFCs) in networks is
>    presented.  Based on these requirements an encapsulation of active
>    OAM message in SFC and a mechanism to detect and localize defects
>    described.  Also, this document updates RFC 8300 in the definition of
>    O (OAM) bit in the Network Service Header (NSH) and defines how the
>    active OAM message identified in SFC NSH.
>
>
>
>
> Please note that it may take a couple of minutes from the time of
> submission
> until the htmlized version and diff are available at tools.ietf.org.
>
> The IETF Secretariat
>
>
> _______________________________________________
> sfc mailing list
> sfc@ietf.org
> https://www.ietf.org/mailman/listinfo/sfc
>


-- 

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

*Gyan Mishra*

*Network Solutions A**rchitect *



*M 301 502-134713101 Columbia Pike *Silver Spring, MD