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

Greg Mirsky <gregimirsky@gmail.com> Thu, 21 May 2020 02:51 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 C65DA3A09D6; Wed, 20 May 2020 19:51:34 -0700 (PDT)
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 wbl2p7iyLYY6; Wed, 20 May 2020 19:51:32 -0700 (PDT)
Received: from mail-lf1-x135.google.com (mail-lf1-x135.google.com [IPv6:2a00:1450:4864:20::135]) (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 317C63A09DF; Wed, 20 May 2020 19:51:32 -0700 (PDT)
Received: by mail-lf1-x135.google.com with SMTP id h188so3611013lfd.7; Wed, 20 May 2020 19:51:31 -0700 (PDT)
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; bh=ik/+JKOxO3RWLpZkwBiNql+yvtiBzUP4fqyT45Lrl6U=; b=YX3H/aWZgyEYtJUjPFlUWDZXixFZu3PgWI4ebHzIXFMAf26GBmZT8au/zfaP1nVe6J rbZ8vKkgRybghg5FeSeSkfnNefPbs5dYZO4eiuBLSsoo8Oh0DctVElH+1aaPzBSbHBt9 ay/inz26frIA6kMxJVLASvbUnPu3n3ymCi3mSreV31IvXt2a3h+5yyJjp8aJrUYhgofw rDvUnZOokW77K5xX50vjIiuj6ks0OcFFzYTEqlAg+E02G1Nr6qdBr+I3dr5TJGLd3Uvk xRzC6Fiv4JeYfpXgAMl3Utt75cUXC3rWQ2Qk65Ey9kyDjGUsWiSdMaCTSAqqJNqQlN63 GmAg==
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; bh=ik/+JKOxO3RWLpZkwBiNql+yvtiBzUP4fqyT45Lrl6U=; b=O+2rNL6DtPZGzMbrgkDx4bM1vGQbF2b7bYbe/Iffdxj5yY32z4+dMbX2yW8mhTrHZQ 83nFfbvTyZbF0/qMAmNO9E77iKFdHXVYj9wPQbuxeY4Bw1etlh438W5o0R4A2jVwCKUO y3rStXj0z2c/e7/5Ip8iU5ZINL0x+G2oQ8V1NwrQXaCfy2p17sthsOiv5jbkE2X7OLyw K+ME1j5Hm2JYmOuXNXCF0DgD2FEzOM9gCpcKhkdbq5I8ZWfkB1eLCKOJeQkh9eQoDvEP KUqNglNxgQ3XZqqlUxgeomJeDFPPLd+uFPedIqgf9HVSatfle8ev79Wf1iWv5kiBf99G QX8w==
X-Gm-Message-State: AOAM5306IlBX0q+Mn+iB8RXhoJWPZdK+JCQmZUYWGJv+M6cQPWzRDJtg 4gbICRtrUwPlqrYaVQcbD40utVHHZ5aUtDkwwKJFcCLt
X-Google-Smtp-Source: ABdhPJxeUJFzyY1WyFcC2nHfkNU7sDEhlGBXaM8eVQzja27Swos8TwIF3LYc9MU/Tf7m2LOVzCGxmntxGAkkb2nu85w=
X-Received: by 2002:a19:c616:: with SMTP id w22mr3760960lff.123.1590029489470; Wed, 20 May 2020 19:51:29 -0700 (PDT)
MIME-Version: 1.0
References: <159002475323.18843.9559672930298713998@ietfa.amsl.com>
In-Reply-To: <159002475323.18843.9559672930298713998@ietfa.amsl.com>
From: Greg Mirsky <gregimirsky@gmail.com>
Date: Wed, 20 May 2020 19:51:17 -0700
Message-ID: <CA+RyBmXXRoPkhXjhpneC8UyBDbxh8P81YDYpRTnbqQiLu64ogQ@mail.gmail.com>
To: Service Function Chaining IETF list <sfc@ietf.org>, sfc-chairs@ietf.org
Content-Type: multipart/alternative; boundary="000000000000e70faa05a61f96b8"
Archived-At: <https://mailarchive.ietf.org/arch/msg/sfc/LkT4W6iHTXZFgBD4WcnaB08S5zw>
Subject: [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: Thu, 21 May 2020 02:51:36 -0000

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