[sfc] Fwd: New Version Notification for draft-wang-sfc-multi-layer-oam-11.txt
Greg Mirsky <gregimirsky@gmail.com> Thu, 26 July 2018 13: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 5F45813114D; Thu, 26 Jul 2018 06:38:02 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.998
X-Spam-Level:
X-Spam-Status: No, score=-1.998 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, 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 g7rWfdap6Kto; Thu, 26 Jul 2018 06:38:00 -0700 (PDT)
Received: from mail-lj1-x241.google.com (mail-lj1-x241.google.com [IPv6:2a00:1450:4864:20::241]) (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 B9747130E25; Thu, 26 Jul 2018 06:37:59 -0700 (PDT)
Received: by mail-lj1-x241.google.com with SMTP id f1-v6so1530186ljc.9; Thu, 26 Jul 2018 06:37:59 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:in-reply-to:references:from:date:message-id:subject:to; bh=0OWU5sMRqPcxWzWzJPfjx/4WZ5zuWUrOpYdt9CpJL4Q=; b=gDaA03FEJT13jLgLY/U7Pfhq3SSU/qE04sC9WT9L2SJVN9oaw4yc2X+xeR6rMXpL4g Yx5JRu6FMmWo3NMEpaJ3+W8t4eCmxA/SpE8OSIagTRAcn4Yot2e9++zovkdAtlLFJAyj tgUJ2Sz6bdc9mfBjCbIBfPFWmi/XDR/1T8zPQTPyzPMh+Q0soHUOzD7VNNqbhS+WPcJL bFPjE/jEfHNaMgJoRUVntfPcobZp+ibdCdtBVEGbLrfuebYm7KXJu9RtK+tOqHmCWSzf VRIpe+qhPsKJcJ8BhQ3S7VWSSTiCG/H5HqycJqAZgNx5zIudK0BcKARieRp+eYBint0W RU5Q==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to; bh=0OWU5sMRqPcxWzWzJPfjx/4WZ5zuWUrOpYdt9CpJL4Q=; b=PEIzrCBM55EG4W11LSdehE2lIHm9o3GQF5acnlS42BRG9lAbDV2H8ILEzsBK/q/ZG+ odCv2/r1k5ovrnkEOWWVEZledp694uSjoNZrDtt1UDbCimNCoIAYLxMARr/70cR5dFu4 qZhF7zWi5rfY22uKbd6P5jDOOG8k1TtBaAySqAjeNBoFNiE+0EMPzfh0W+50cW8/CD29 HE9odFN4Yb8BOYDrjhw7g2ITsapQELZyZlIGjjO85nBpbo5qD0iwZk+3Dw+LrIIdd0xZ h7WbKfPrjg0cYxgRyESJP6lNN54Z0OelUbEpu6bT+SmOvocOK7CXMAEXXt81AF0RUbT4 3tKg==
X-Gm-Message-State: AOUpUlEa5C3Lx6atRtM6N/8aKnGnGAxkKokIYq0/7Yc7Ye+zkCGtBhrJ jxxJEKfloagXA83B/Vce7UhV5fWR4Fj7rSvAhA0YTw==
X-Google-Smtp-Source: AAOMgpfTnTLvutkCjYowNyKbz9HFnhX9EXA7fbe4vk0TBkqrV1L4TZ4l429Vr3UpIBGeYcVMbvpPSFaQCPmrgI7wDaU=
X-Received: by 2002:a2e:91d6:: with SMTP id u22-v6mr1750009ljg.64.1532612277634; Thu, 26 Jul 2018 06:37:57 -0700 (PDT)
MIME-Version: 1.0
Received: by 2002:a2e:709:0:0:0:0:0 with HTTP; Thu, 26 Jul 2018 06:37:56 -0700 (PDT)
In-Reply-To: <153261171809.25844.2131898629664559414.idtracker@ietfa.amsl.com>
References: <153261171809.25844.2131898629664559414.idtracker@ietfa.amsl.com>
From: Greg Mirsky <gregimirsky@gmail.com>
Date: Thu, 26 Jul 2018 06:37:56 -0700
Message-ID: <CA+RyBmVs3C6ZdcnAG5CPYhsqDEMc1tuj90F00S_KoRWUSie1UQ@mail.gmail.com>
To: Service Function Chaining IETF list <sfc@ietf.org>, sfc-chairs@ietf.org
Content-Type: multipart/alternative; boundary="0000000000006309810571e71a0c"
Archived-At: <https://mailarchive.ietf.org/arch/msg/sfc/aToXs0jvXtRfJgLBF8VKYuVSXr4>
Subject: [sfc] Fwd: New Version Notification for draft-wang-sfc-multi-layer-oam-11.txt
X-BeenThere: sfc@ietf.org
X-Mailman-Version: 2.1.27
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, 26 Jul 2018 13:38:02 -0000
Dear All, we've updated this draft to position it as the definition and introduction of active OAM in SFC NSH in networks. Also, we've added text to clarify how active OAM is identified in NSH. Appreciate your reviews, questions, comments, and suggestions. Dear WG Chairs, we believe that the draft is stable, readable, and addresses very much needed technical aspect of OAM in SFC, to empower operators with the right tools to operate SFC in networks. Appreciate your consideration to issuing a call for WG adoption of this draft. Regards, Greg ---------- Forwarded message ---------- From: <internet-drafts@ietf.org> Date: Thu, Jul 26, 2018 at 6:28 AM Subject: New Version Notification for draft-wang-sfc-multi-layer-oam-11.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-11.txt has been successfully submitted by Greg Mirsky and posted to the IETF repository. Name: draft-wang-sfc-multi-layer-oam Revision: 11 Title: Active OAM for Service Function Chains in Networks Document date: 2018-07-26 Group: Individual Submission Pages: 15 URL: https://www.ietf.org/internet-drafts/draft-wang-sfc-multi- layer-oam-11.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-11 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-11 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