[sfc] Fwd: New Version Notification for draft-ietf-sfc-multi-layer-oam-01.txt
Greg Mirsky <gregimirsky@gmail.com> Tue, 29 January 2019 01:52 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 15C6F12875B for <sfc@ietfa.amsl.com>; Mon, 28 Jan 2019 17:52:49 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.999
X-Spam-Level:
X-Spam-Status: No, score=-1.999 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-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 I_0n9PfUqGHn for <sfc@ietfa.amsl.com>; Mon, 28 Jan 2019 17:52:47 -0800 (PST)
Received: from mail-lj1-x234.google.com (mail-lj1-x234.google.com [IPv6:2a00:1450:4864:20::234]) (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 E5781127B4C for <sfc@ietf.org>; Mon, 28 Jan 2019 17:52:46 -0800 (PST)
Received: by mail-lj1-x234.google.com with SMTP id s5-v6so16009126ljd.12 for <sfc@ietf.org>; Mon, 28 Jan 2019 17:52:46 -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; bh=fp8FX8YF1T0PTcZOFMibn283ubziBVAGudpsrhZ1NYE=; b=vRygL/wuhjU+5OXYrSG1S5rHzchsOwKe9AT31r4ViVbjBAkfdvbLv8hbMjSxGWD2lm Iims1x4ayxgRwGKIBld9YOZjB8mJLZ32IBjJ2+U2rgR44Q1ZYZwInaVEjXeexu1A3K+1 xSZ/y+t9vx0OAdnoOip7Hp+2zG05LDqS0cSZIGdgPH0Px1LTIpfMNaitcaWTWy/SSw3I nMqt9xin0p46V9uOnKaLvcFZ8H6QVyCrNzEIRu/JwmPVVkPyX43Bt3a+i8q2eT+fZD73 flQXv/+QAcFrhx7kHenm3qYSJ4jUQM0wxiGhC8AQkS43na8lJgvlwsn/D/yoB/kffTZN wgxA==
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=fp8FX8YF1T0PTcZOFMibn283ubziBVAGudpsrhZ1NYE=; b=BebIBOlqTLH3Ayr038AH9qDPvU/uTkOzzXITyzxmumyqiDQw8v0KXnZFfnlv3qTPXe v4sKyxUYhJN5eZxNXrVpyj6TGbbnv0WyMNXS+UfN7tXafvaUOMxs07cpKPVBLcFqHzcr HPZ0loL0nbQsCNPWWSBa6mP/vOt/o2hMJb/Vkgq4LlH5GeMOnhQNlQeW9fucmn3Fb2+I fL8k125bpGwwstwZLmQPUcF9oB8K9sGJSfXq2h3TCXjoK6359PeE+Cs8kA1EPbbs5zOY 3T2Sdj4zVXWk658L0IPplaRT4OOsNSm+cpcwrkunwhMSUI1k/iEFHWuWsYfCSjzJp9oj U9uw==
X-Gm-Message-State: AJcUukcnPo1iDmpp0l/VayepSBGkA7vppii2mvWaNQu+9EY9+KmNDsE3 5m5MS2uhQEjQCp7RuJF3G7zRzoBQIozRk/oH73CdqbD9
X-Google-Smtp-Source: ALg8bN4gKWK9SRgOU+LRtjuaFw6g2hpqcTnTBFM1pfJqMrRhopE+H6m+Tv9dmnL/SpSeWwJUfb6eKe3TZWZmcGeJSms=
X-Received: by 2002:a2e:9f0b:: with SMTP id u11-v6mr17399968ljk.99.1548726764517; Mon, 28 Jan 2019 17:52:44 -0800 (PST)
MIME-Version: 1.0
References: <154872650456.3046.12486139930224299393.idtracker@ietfa.amsl.com>
In-Reply-To: <154872650456.3046.12486139930224299393.idtracker@ietfa.amsl.com>
From: Greg Mirsky <gregimirsky@gmail.com>
Date: Tue, 29 Jan 2019 09:52:35 +0800
Message-ID: <CA+RyBmW349=KNd2YyoRjvwywNsg3SDKoznmuxgc=+k4ib9v8bw@mail.gmail.com>
To: Service Function Chaining IETF list <sfc@ietf.org>
Content-Type: multipart/alternative; boundary="000000000000a73e0005808f0c52"
Archived-At: <https://mailarchive.ietf.org/arch/msg/sfc/7Epy12hac2_AZyMezv9FjftItJI>
Subject: [sfc] Fwd: New Version Notification for draft-ietf-sfc-multi-layer-oam-01.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, 29 Jan 2019 01:52:49 -0000
Dear All, this version includes updates to address (apologies it took too long) comments received at our meeting in Bangkok from Adrian. Much appreciate your reviews, comments, and question on the draft. Regards, Greg ---------- Forwarded message --------- From: <internet-drafts@ietf.org> Date: Tue, Jan 29, 2019 at 9:48 AM Subject: New Version Notification for draft-ietf-sfc-multi-layer-oam-01.txt To: <sfc-chairs@ietf.org>, Gregory Mirsky <gregimirsky@gmail.com>, Bhumip Khasnabish <vumip1@gmail.com>, Wei Meng <meng.wei2@zte.com.cn>, Cui(Linda) Wang <lindawangjoy@gmail.com> A new version of I-D, draft-ietf-sfc-multi-layer-oam-01.txt has been successfully submitted by Greg Mirsky and posted to the IETF repository. Name: draft-ietf-sfc-multi-layer-oam Revision: 01 Title: Active OAM for Service Function Chains in Networks Document date: 2019-01-28 Group: sfc Pages: 15 URL: https://www.ietf.org/internet-drafts/draft-ietf-sfc-multi-layer-oam-01.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-01 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-01 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