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

Greg Mirsky <gregimirsky@gmail.com> Wed, 09 December 2020 06:58 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 A36F73A0D06; Tue, 8 Dec 2020 22:58:15 -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 KRpHwdTAQ8Hx; Tue, 8 Dec 2020 22:58:11 -0800 (PST)
Received: from mail-lj1-x236.google.com (mail-lj1-x236.google.com [IPv6:2a00:1450:4864:20::236]) (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 4BE9A3A0B26; Tue, 8 Dec 2020 22:58:11 -0800 (PST)
Received: by mail-lj1-x236.google.com with SMTP id t22so1015011ljk.0; Tue, 08 Dec 2020 22:58:11 -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=g43N6xQGcC1tYZsIkkeZ7GvPCIaVZU54FW10Vl2fKps=; b=H9Y5mUBDuqRZUdYzAeVfQjFU4NlAtXI2SFIidu7gHXkAfOpEzIdshyTYq1Fj+J5je+ RcRO26Ubrre1uf0UlJ5pxSUhvlwpkhh+xJV2JOtEiLHA/HryVDue3qmcM2IY/yjfPCwb DKOd0zl+z1gSENymJgFbvzbmEXVM2iBY8Z0ufCB9mynK2M7aEf9pKvXjmk4sG7GxPhWl A/lDQ57N64+/Ds08tKZus4+T/G9M31a7X0CWzlQn0ymrjMI+ArKWE5N3lgpInqoGzzAP Pb01jOB3KA1AubJ3Rx3FFH3Zugu6s+XzklyN9TwRQEqtz9VURqD1Mc5vM2mO/iLEMEZs M4SA==
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=g43N6xQGcC1tYZsIkkeZ7GvPCIaVZU54FW10Vl2fKps=; b=A+dZX5tnmkWYz/SQeAdK1k+XPz1H8edabYeIFOx0k/kl1SlOSPOnE4Km9pve6cJ8hq 2604kyTfPlgi3kW9Ce4SOx7clnPmWM24/C3/e20WcKbU5d+sbKMK6s3c7s460ETCsMa8 riz3V+TfHJG3NCH1ZSN7H2slnaE++6zOc/DNWMbUNdN0qw4iMrh6NFR0duyn54qBhuNl 8fE1VszbpC5SzpeAsRdLwqvm70CoGoIcpCAVc1Oy0zVTvChes4KhDkANBtVD9tM+OnVn dw4zzAbPxxMqsEo4e4xxVo9Gtm+rwqOWIGcksCTr/7dJKiQJr6QvTuc4VtFdRL9cGFlZ OWkA==
X-Gm-Message-State: AOAM531ah9caDwoTn/wQnKJvcfV4ImA8neMc939Zoswk6wwT9bN+bzKH 5qBGT11qQwSZwIDwT8DWFXVGlBuwFPmRWK+wnZE=
X-Google-Smtp-Source: ABdhPJz/Noe/xgZkCKj+7U7xH2HzQ2HKcNgG5Qvc3P00+2bQ/b/G4lzkOMa6T10N4XQ0XwCR99aF4D2DcqpaltL6l/Y=
X-Received: by 2002:a2e:9a95:: with SMTP id p21mr509784lji.245.1607497089387; Tue, 08 Dec 2020 22:58:09 -0800 (PST)
MIME-Version: 1.0
References: <159002475323.18843.9559672930298713998@ietfa.amsl.com> <CA+RyBmXXRoPkhXjhpneC8UyBDbxh8P81YDYpRTnbqQiLu64ogQ@mail.gmail.com> <CABNhwV2MGC8pc8hGZGDK1LSs+dZ54mBOD9t6K=Ci0E95bvxO7w@mail.gmail.com>
In-Reply-To: <CABNhwV2MGC8pc8hGZGDK1LSs+dZ54mBOD9t6K=Ci0E95bvxO7w@mail.gmail.com>
From: Greg Mirsky <gregimirsky@gmail.com>
Date: Tue, 08 Dec 2020 22:57:57 -0800
Message-ID: <CA+RyBmW-NnQo0Bq3VFcrkJXF9k0FzRsSQa5fAJiw2hzzTFjkJA@mail.gmail.com>
To: Gyan Mishra <hayabusagsm@gmail.com>
Cc: Service Function Chaining IETF list <sfc@ietf.org>, sfc-chairs@ietf.org
Content-Type: multipart/alternative; boundary="000000000000fd8f5805b60294f7"
Archived-At: <https://mailarchive.ietf.org/arch/msg/sfc/6FhugsX51v4ZLjLBIfPzEa1BgPQ>
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: Wed, 09 Dec 2020 06:58:16 -0000

Hi Gyan,
thank you for your interest in the SFC OAM work and your thoughtful
suggestion. Indeed, every moving part we introduce in a network must
include a robust security mechanism. We'll work on a solution and hope to
share our proposal with you and the group soon.

Regards,
Greg

On Mon, Dec 7, 2020 at 5:47 PM Gyan Mishra <hayabusagsm@gmail.com> wrote:

> 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
>
>