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

Greg Mirsky <gregimirsky@gmail.com> Wed, 10 July 2019 22:33 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 135601201E5 for <sfc@ietfa.amsl.com>; Wed, 10 Jul 2019 15:33:40 -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 9ICmcyz8Lcsn for <sfc@ietfa.amsl.com>; Wed, 10 Jul 2019 15:33:38 -0700 (PDT)
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 606C612004F for <sfc@ietf.org>; Wed, 10 Jul 2019 15:33:38 -0700 (PDT)
Received: by mail-lf1-x133.google.com with SMTP id z15so2658690lfh.13 for <sfc@ietf.org>; Wed, 10 Jul 2019 15:33:38 -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=2nL0CCNiX8DpyB+c2JAljwUjfBnz+4h+GmDsXzCDf1s=; b=QNTO6bN+Q2mrwUiU+trKe2xoDZyEyNskHjdEGwSVlxQejVtej0dDFKX46lYRBz2G9/ yteNiihkFLasNCEAe62Vty4vDjcBf6jgOYJnHr8jTGB/CdkTrpbgVMtdJXQVTGSvvcuG YVx+NTbUdwXx4iUiIUaiobrkFwVdZlevt2MyLraAmnJozBsNchQs92WTZohAT5urEl+o Q73Tj6VswnO71/T04v5fahLc0uChnUT85edLEwcltgu6E2Ba7yQvS9IF0lLvjLKNtDYH eT0HePFOXoECRWjsK1iioy1ZLdDqhimFd+VEbHTXFFhjkXLjmUKVb1JXhUS1A/nbATH9 ALlw==
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=2nL0CCNiX8DpyB+c2JAljwUjfBnz+4h+GmDsXzCDf1s=; b=fT5X76x4EmaKhQbp1WV2RlznlJUi/49r+rpdyyhMj9CQM3pqfQYZDqc9Ds8QrmIev8 OgcO3V3Uf4VbZcpaLgQE2PZ9//5mPms8QrkdEPj0Ym9KZa1uD4QDtHZrgsLEQtIhNJgf dYGhb4ipaFB0DyfIKsJmtCQnFAs8GP4zfWDcYHrfdf5OBKXmWbzlwUGObKGC6McIMVre XzCDSqB+/mJPDaRFg7MlYzBnuuTz8ThBHQnm3J0gNnsjrUCWm5nQ5wdAgc9eT7152kJU azNo1LaFxgrhNs+ZS6QiLdJ8lpHACe3WghrxT654kc7epnbLZ8IdXraEiTSg2ng+CEWz kvTA==
X-Gm-Message-State: APjAAAXFxtoVQ/pNlP/kFeUPKWCsWWk4kPg5cvbrqNjZhjjaVJkmNtFC KLlc5A2m4NXmEMrNAWwHmGdVIof16KU2MiV6FbI=
X-Google-Smtp-Source: APXvYqzKYUNpiNCE+J+rXWUmrwTFJQBshUI7Zvx/KE5Z20cwLphobTdNBkYhWfQIXZe8hxEtDEolYlRFJye+xW7SgcA=
X-Received: by 2002:a19:9111:: with SMTP id t17mr33390lfd.113.1562798016377; Wed, 10 Jul 2019 15:33:36 -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: Wed, 10 Jul 2019 15:33:24 -0700
Message-ID: <CA+RyBmWEbrk5rY8XpvTKVAqOzcdWAGDzVn1p=Fjgzfg8yOTMGA@mail.gmail.com>
To: James Guichard <james.n.guichard@futurewei.com>
Cc: "sfc@ietf.org" <sfc@ietf.org>
Content-Type: multipart/alternative; boundary="0000000000009f383b058d5b442d"
Archived-At: <https://mailarchive.ietf.org/arch/msg/sfc/qV4Nv2rMiKKMCMyASvvjJwER7VA>
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: Wed, 10 Jul 2019 22:33:40 -0000

Hi Jim, Joel, et al.,
I have a question about the scope of the SFC OAM Framework. In Section 1.1
the scope is defined as:
   The focus of this document is to provide an architectural framework
   for SFC OAM, particularly focused on the aspect of the Operations
   component within OAM.  Actual solutions and mechanisms are outside
   the scope of this document.
But after reading it several times over, I believe that the scope of the
document is more narrow and includes only OAM for SFC NSH. I couldn't find
any discussion of OAM for SFC based on RFC 8595, nor I could find it being
referenced in the framework. If it is outside the scope of this document,
should it provide an explanation, identify it as an outstanding work for
the future?

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
>