[sfc] Fwd: New Version Notification for draft-ao-sfc-oam-path-consistency-09.txt

Greg Mirsky <gregimirsky@gmail.com> Tue, 15 December 2020 03:28 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 6628D3A00E0; Mon, 14 Dec 2020 19:28:30 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.197
X-Spam-Level:
X-Spam-Status: No, score=-0.197 tagged_above=-999 required=5 tests=[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 0FFwmPodTx4u; Mon, 14 Dec 2020 19:28:28 -0800 (PST)
Received: from mail-lf1-x133.google.com (mail-lf1-x133.google.com [IPv6:2a00:1450:4864:20::133]) (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 355273A00D8; Mon, 14 Dec 2020 19:28:28 -0800 (PST)
Received: by mail-lf1-x133.google.com with SMTP id 23so35666886lfg.10; Mon, 14 Dec 2020 19:28:28 -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=m0Y7P6dDN+TKJMSEJbTp4CBvKw8kPlF+dn5QMfTH7Cw=; b=COnwzdO8P1lk08BfbTfHdpSqfiZdg+DcGlXyWQciXna+rT0WNtP7KkLqBw9i2apVq0 +DsVU+JfuYv13JlVLLb16UDv89gQySw5Xl67PkQx5Xm5Sxemhw6BbHp4ASiUuyRE2Lng drQEzzsF53Wgi6OJT4cKO0jxnMt51rV8SjuhSxupXwr+KjibPy2gH47j3llqxWXbU6Xr EJFxLMg9LGlz2jfcAuvkk3uKZEpPBVb/F+pEIHxwdwIDtgJkxUwy84XcakV9WV9m71+y rHRz/+cq3gZVwFEGxG6foAyHHOFWnh2fWcjwM1d2hHKozCRLhpnp70HV0cohW3qDR6UP EOFA==
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=m0Y7P6dDN+TKJMSEJbTp4CBvKw8kPlF+dn5QMfTH7Cw=; b=VthBl8M9p5I37udxiNWjNzvFY+fauVZ2XCarrKgxi+wWrlWL/VvmmTMu39TzA35t+j u6yIVsw0zQqzQz6vh1VF3DrB42XLpY4tHPU7FQ3HUffctw/3jIbi5DwQzTabe9LAJS4v c8X/WuBjYXvzsTCVz+DZAdwsh6Fe52TDx2u04tzsahZFdAnEc/5Yg638rC/PHLNJ9nsL /Lwx7vIrJGuR8ITyEccYuJgwbBMcK7tarswJsfPLjh8+95ez4Wf6+z7RLBbfENg19pqF XSIihwn09y7WVZoDHcFvDffa9Yr7ZhUK/oDjQujw2BiEMhlOpY09Bfv8SisyDnNClw4/ VQbg==
X-Gm-Message-State: AOAM531U5dmwjuUo0tlU1RcJ3Bo+KEQkV/1YZaS27lE0rmxpOkrWLqO9 AeoyVj02sxIozlRkNWAmSoe7QGaV6r0Fy6/D5D/uIKP5v5Y=
X-Google-Smtp-Source: ABdhPJw1nBqikshKb2YpjrSUxtSgwYAidrDCcwB9ikrnx6iFoGO6iguWDb0w6Bn+3xorn9e0U+FG3hITQdKMBXwSARA=
X-Received: by 2002:a05:6512:318b:: with SMTP id i11mr9985356lfe.364.1608002906144; Mon, 14 Dec 2020 19:28:26 -0800 (PST)
MIME-Version: 1.0
References: <160800250337.21018.7045786732742968155@ietfa.amsl.com>
In-Reply-To: <160800250337.21018.7045786732742968155@ietfa.amsl.com>
From: Greg Mirsky <gregimirsky@gmail.com>
Date: Mon, 14 Dec 2020 19:28:15 -0800
Message-ID: <CA+RyBmWs9D7wBT3D3133Muj5+JPo8cddFT1ZFBP1KY6zH1iNvg@mail.gmail.com>
To: Service Function Chaining IETF list <sfc@ietf.org>, sfc-chairs@ietf.org
Content-Type: multipart/alternative; boundary="00000000000004c1e505b6785ad1"
Archived-At: <https://mailarchive.ietf.org/arch/msg/sfc/X6ln4EmJpxo5FE6lLbLqNAhB0Hs>
Subject: [sfc] Fwd: New Version Notification for draft-ao-sfc-oam-path-consistency-09.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, 15 Dec 2020 03:28:30 -0000

Dear All,
the authors are glad to welcome Gyan Mishra joining in the work on the
draft.
Also, the use of the new Authentication TLV is now described in the
document. The integrity of the SFF Information Record TLV in the SFC Echo
Reply can be protected using the Authentication TLV.

We always welcome your comments, questions, and suggestions.
The authors believe that the document is ready for adoption by the SFC WG
and greatly appreciate your consideration.

Regards,
Greg (on behalf of the authors)

---------- Forwarded message ---------
From: <internet-drafts@ietf.org>
Date: Mon, Dec 14, 2020 at 7:21 PM
Subject: New Version Notification for
draft-ao-sfc-oam-path-consistency-09.txt
To: Zhonghua Chen <18918588897@189.cn>, Greg Mirsky <gregimirsky@gmail.com>,
Kent Leung <kleung@cisco.com>, Ting Ao <18555817@qq.com>, Gyan Mishra <
gyan.s.mishra@verizon.com>



A new version of I-D, draft-ao-sfc-oam-path-consistency-09.txt
has been successfully submitted by Greg Mirsky and posted to the
IETF repository.

Name:           draft-ao-sfc-oam-path-consistency
Revision:       09
Title:          SFC OAM for path consistency
Document date:  2020-12-14
Group:          Individual Submission
Pages:          12
URL:
https://www.ietf.org/archive/id/draft-ao-sfc-oam-path-consistency-09.txt
Status:
https://datatracker.ietf.org/doc/draft-ao-sfc-oam-path-consistency/
Htmlized:
https://datatracker.ietf.org/doc/html/draft-ao-sfc-oam-path-consistency
Htmlized:
https://tools.ietf.org/html/draft-ao-sfc-oam-path-consistency-09
Diff:
https://www.ietf.org/rfcdiff?url2=draft-ao-sfc-oam-path-consistency-09

Abstract:
   Service Function Chain (SFC) defines an ordered set of service
   functions (SFs) to be applied to packets and/or frames and/or flows
   selected due to classification.  SFC Operation, Administration and
   Maintenance can monitor the continuity of the SFC, i.e., that all SFC
   elements are reachable to each other in the downstream direction.
   But SFC OAM must support verification that the order of traversing
   these SFs corresponds to the state defined by the SFC control plane
   or orchestrator, the metric referred to in this document as the path
   consistency of the SFC.  This document defines a new SFC active OAM
   method to support SFC consistency check, i.e., verification that all
   elements of the given SFC are being traversed in the expected order.




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