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

Greg Mirsky <gregimirsky@gmail.com> Mon, 08 October 2018 19:38 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 E0985130FA5; Mon, 8 Oct 2018 12:38:25 -0700 (PDT)
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 exlDXtPo7-53; Mon, 8 Oct 2018 12:38:23 -0700 (PDT)
Received: from mail-lf1-x144.google.com (mail-lf1-x144.google.com [IPv6:2a00:1450:4864:20::144]) (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 058B1127148; Mon, 8 Oct 2018 12:38:22 -0700 (PDT)
Received: by mail-lf1-x144.google.com with SMTP id w21-v6so14773490lff.6; Mon, 08 Oct 2018 12:38:22 -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=u/POGRl7RKBH8zH0d/iOuMSdfwIu8ssrOo7pt9MrOGE=; b=LhRvOwUDRMQzkrsf8oiyH0NMt/Y+ubQBfibQqxPIbiGAZKrhmMjpOGjLf0LB5WI2on kFsX5tO57ZiPDtEt0UFwDbn5WqS13uZ3vQgvekr9myq9ubEraJoyRVGFbMWWzVQUPxzi ftikcWFh3/yEAuT1rwu4iWlhPQ6xf5GkkYSQ28+7/hmrQzcesit0D6OOdwXPTp2cJXRu Newj2EX8VroC5EK2kMnwREhUQJtSrKD6knAm9VsB2JTTwc85T4g90aPf2XY2LhR8A3CR FMkhnOscMoZSXhf+h+bE3tcHaRf6FugF0bKZ9n/moAFCi2nAgiLO68s7PXs4oOCqfmYD QyHg==
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=u/POGRl7RKBH8zH0d/iOuMSdfwIu8ssrOo7pt9MrOGE=; b=V1Y/96/xr6zxn44XXQ1lE0k9lqT+49SYSRSjqx4fguoKuzIC+/lxBzMm3kbG7e2PIA kpQgPxdIot8otWYVtMNLInK4GRcxi8AQrxm6n+Rl3x7u0z49oASy/cMJO2swWwj9Lh9l rno7kSSVA5ZBzeJ/s5nssc6k2h3IsTw+rmC3g9uKJeoOQ3I1zo+bMEwx4l9N4BULd3o+ VZI6CEflxLqi7RepGUO3uQOvkA0GcE2hHNz5QNjJQH5ws2PZyMadaZZxyJ+6Z4eWaZ9m J6zTO1KzykJKVP8yXB/nXHoNTlWr2oXlp/mVJ/N6N5YVAGSZ1UxVZyNIh1Ae9+OiIpqJ ecDw==
X-Gm-Message-State: ABuFfoh228c1nG+ZeXOM2MgapnZnqlG36vmqs9pDFcX4/4Uy4KM/2ytW JbRsZ7bTOysGLCVJ8SJhKtWC+3yEEf5IivDvm6pI2w==
X-Google-Smtp-Source: ACcGV61FOTtIX4fceBDARVDyvVZYAxJLXoKBIMC5gSSaG3P/CfIozaSe9apAEzNtXrJxvA1wJkylJmhMLlnYNmHlvqo=
X-Received: by 2002:a19:9cd4:: with SMTP id f203-v6mr13259002lfe.76.1539027500619; Mon, 08 Oct 2018 12:38:20 -0700 (PDT)
MIME-Version: 1.0
References: <153902668548.18373.15525830154074476300.idtracker@ietfa.amsl.com>
In-Reply-To: <153902668548.18373.15525830154074476300.idtracker@ietfa.amsl.com>
From: Greg Mirsky <gregimirsky@gmail.com>
Date: Mon, 08 Oct 2018 12:38:08 -0700
Message-ID: <CA+RyBmWjxmu7=BFdyHfc9Rs+zYd7fWTg4xOWs0LWSg-AY51EUQ@mail.gmail.com>
To: Service Function Chaining IETF list <sfc@ietf.org>, sfc-chairs@ietf.org
Content-Type: multipart/alternative; boundary="000000000000795cb10577bcc346"
Archived-At: <https://mailarchive.ietf.org/arch/msg/sfc/Rk_KPVQaS2dGuvUc2KXeUmtJ9Hw>
Subject: [sfc] Fwd: New Version Notification for draft-wang-sfc-multi-layer-oam-12.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: Mon, 08 Oct 2018 19:38:26 -0000

Dear All,
the update adds to the discussion in Section 4 of how SFC OAM identified in
NSH. The rules state how the values of O bit and the Next Protocol field
should be set in case of OAM included in TLVs, or as payload immediately
following NSH.
Your comments, questions always welcome and much appreciated.
Also, authors ask the WG Chairs kindly consider WG adoption of this work.

Regards,
Greg

---------- Forwarded message ---------
From: <internet-drafts@ietf.org>
Date: Mon, Oct 8, 2018 at 12:24 PM
Subject: New Version Notification for draft-wang-sfc-multi-layer-oam-12.txt
To: Bhumip Khasnabish <bhumip.khasnabish@ztetx.com>, Gregory Mirsky <
gregimirsky@gmail.com>, Wei Meng <meng.wei2@zte.com.cn>, Cui(Linda) Wang <
lindawangjoy@gmail.com>



A new version of I-D, draft-wang-sfc-multi-layer-oam-12.txt
has been successfully submitted by Greg Mirsky and posted to the
IETF repository.

Name:           draft-wang-sfc-multi-layer-oam
Revision:       12
Title:          Active OAM for Service Function Chains in Networks
Document date:  2018-10-07
Group:          Individual Submission
Pages:          15
URL:
https://www.ietf.org/internet-drafts/draft-wang-sfc-multi-layer-oam-12.txt
Status:
https://datatracker.ietf.org/doc/draft-wang-sfc-multi-layer-oam/
Htmlized:
https://tools.ietf.org/html/draft-wang-sfc-multi-layer-oam-12
Htmlized:
https://datatracker.ietf.org/doc/html/draft-wang-sfc-multi-layer-oam
Diff:
https://www.ietf.org/rfcdiff?url2=draft-wang-sfc-multi-layer-oam-12

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