IETF Logo Mail Archive

Re: [sfc] WG Last Call draft-ietf-sfc-oam-framework-06

Greg Mirsky <gregimirsky@gmail.com> Tue, 09 July 2019 01:50 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 11FAB12006E for <sfc@ietfa.amsl.com>; Mon, 8 Jul 2019 18:50:53 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.702
X-Spam-Level:
X-Spam-Status: No, score=-0.702 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, PDS_NO_HELO_DNS=1.295, RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=no 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 sgLtgeyZD7Pz for <sfc@ietfa.amsl.com>; Mon, 8 Jul 2019 18:50:51 -0700 (PDT)
Received: from mail-lf1-x12e.google.com (mail-lf1-x12e.google.com [IPv6:2a00:1450:4864:20::12e]) (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 52C93120047 for <sfc@ietf.org>; Mon, 8 Jul 2019 18:50:51 -0700 (PDT)
Received: by mail-lf1-x12e.google.com with SMTP id r15so12222077lfm.11 for <sfc@ietf.org>; Mon, 08 Jul 2019 18:50:51 -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 :cc; bh=oeYNPj41/KqpFnCn31OSZ2T7DHe8F3VN9cAXqW1PFvo=; b=dNA0x1TJux348NtbX6zubP4vammMSWUaOd4nhDAMFWNtiwADt2dggTs051ldKkZofD U8xvCrkqAkmn+mMDOsFL6FqDSLXic/al6dEzTaoW0ZWprlN7tPWOmSHZYop/abnNPYnv fMTF7qRD1fgORYEDARiP0KbWy9s8MWC3ij6zSu11C1Obtq9vgEKrfVNrYKWydU+8P+km fAzsLe/StwQKG1edXYrQ1zSaT5q5D6HTawIyWNcJkKvvL84kMhqBILsrxwWf5PkkfB++ jmsae2WJujL3qvTcR0WcxD/IdNG+Y1M+dxBnDPH8XAnROTraTZr8b2bdlBAY//NWeMzG tZag==
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:cc; bh=oeYNPj41/KqpFnCn31OSZ2T7DHe8F3VN9cAXqW1PFvo=; b=GwxYaP4NrqvHBLp2AuRXyHgJqFbwQW+QI7I303oO/QqGUreD3ztSQwOL2hI4OqDscM 69ciKkdo6ytUsWzfDoXBef4yodiSRYhcAXJzCjOe/zY12EuPb2c1h6okfGLksT3x5gtT NxfXnQVm4hJsub8YE3TyOaIKABrmR88GSMEIv29uZLa/lOleMGIEPmU6+mvB+ddYSBHx jfbOnKheXJkJicpJCOxDvOP0vJuEt8OqiPVI8thrmzCFk9+oKsyQ+3ycbjsJt/fjP2Ab 08ocwXVS9ohOGjx9lGn35bbojmofkhTwjDc2dVmAnRo8i60IT3cyvFGlFeiQroVXYBZz Zt7g==
X-Gm-Message-State: APjAAAWh8FQYMK6Q0+gyALqS5PS5qf4fDho7L6ThmE9IFXUG8SiI51Y0 RU/USC2nXKB0S40vPEp8Fz3zsvzqIyJtrHQJAbk=
X-Google-Smtp-Source: APXvYqyrRAQpBmT4PBmypcQBJ9+BAatZ4tcttrtaBpzYHEQYSUv9YU2M/5a42pOR6cwxjYWtmSBNvce52yX8iqWNP5k=
X-Received: by 2002:a19:9111:: with SMTP id t17mr10100888lfd.113.1562637049523; Mon, 08 Jul 2019 18:50:49 -0700 (PDT)
MIME-Version: 1.0
References: <BYAPR13MB25978FD458B59EB22067685FD21E0@BYAPR13MB2597.namprd13.prod.outlook.com>
In-Reply-To: <BYAPR13MB25978FD458B59EB22067685FD21E0@BYAPR13MB2597.namprd13.prod.outlook.com>
From: Greg Mirsky <gregimirsky@gmail.com>
Date: Mon, 08 Jul 2019 18:50:38 -0700
Message-ID: <CA+RyBmWK9C+2UOxAG7BzRydJ2xWJNpQ1iApu_L2tCagQr48Mkg@mail.gmail.com>
To: James Guichard <james.n.guichard@futurewei.com>
Cc: "sfc@ietf.org" <sfc@ietf.org>
Content-Type: multipart/alternative; boundary="0000000000003ff401058d35ca9f"
Archived-At: <https://mailarchive.ietf.org/arch/msg/sfc/45cjSW8qJDI3_xlM5HPMY2n43_s>
Subject: Re: [sfc] WG Last Call draft-ietf-sfc-oam-framework-06
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, 09 Jul 2019 01:50:53 -0000

Hi Jim,
I've reviewed the latest version of the document and find that many of my
earlier comments, questions have not yet been answered, addressed. In
particular, I'd like to return to the question I've asked authors What is
"availability"? As we know, OAM provides tools for Fault Management and
Performance Monitoring ('F' and 'P' in FCAPS). Where does "availability",
as discussed in this document,  fit? Is it to detect a defect? Or is it a
performance metric? If it is the former, then how it is related to other
known FM OAM methods - connectivity verification and continuity check? If
it is the latter,i.e., performance metric, then how it is measured? What is
the unit of "availability" - second, number of packets?
I've asked this question and have to bring it up again because I don't see
in the document an explanation, definition, or reference to an existing
document.
I hope that the WG and you ask authors to address my comment and questions.
Please note that I'm preparing more comments on the current version and
will share them later this week (apologies, had to beat the IETF cut-off
submission deadline).

Regards,
Greg

On Tue, May 28, 2019 at 7:37 AM James Guichard <
james.n.guichard@futurewei.com> wrote:

> Dear WG:
>
>
>
> This message starts a new two week WG Last Call on advancing
> https://datatracker.ietf.org/doc/draft-ietf-sfc-oam-framework/
> <https://nam03.safelinks.protection.outlook.com/?url=https%3A%2F%2Fdatatracker.ietf.org%2Fdoc%2Fdraft-ietf-sfc-oam-framework%2F&data=02%7C01%7Cjames.n.guichard%40futurewei.com%7Ce47e5eb13f224f18c46408d6e378b2f7%7C0fee8ff2a3b240189c753a1d5591fedc%7C1%7C0%7C636946504868870205&sdata=lkKvAgmKik7lkqGANQpnIvBRdbjKAqYtzTUdTfB9f3Y%3D&reserved=0>
> for publication as an Informational RFC.
>
>
>
> Substantive comments and statements of support for publishing this
> document should be directed to the mailing list. Editorial suggestions can
> be sent to the authors.  This last call will end on 11th June 2019.
>
>
>
> Thanks!
>
>
>
> Jim & Joel
>
>
>
>
> _______________________________________________
> sfc mailing list
> sfc@ietf.org
> https://www.ietf.org/mailman/listinfo/sfc
>

v2.23.0 | Report a Bug | By Email