Re: [bess] John Scudder's Discuss on draft-ietf-bess-evpn-oam-req-frmwk-08: (with DISCUSS and COMMENT)

Donald Eastlake <d3e3e3@gmail.com> Tue, 13 April 2021 01:08 UTC

Return-Path: <d3e3e3@gmail.com>
X-Original-To: bess@ietfa.amsl.com
Delivered-To: bess@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 61D553A19EA; Mon, 12 Apr 2021 18:08:51 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.847
X-Spam-Level:
X-Spam-Status: No, score=-1.847 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, FREEMAIL_ENVFROM_END_DIGIT=0.25, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, 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 TVWCLPVrI1GS; Mon, 12 Apr 2021 18:08:47 -0700 (PDT)
Received: from mail-io1-xd36.google.com (mail-io1-xd36.google.com [IPv6:2607:f8b0:4864:20::d36]) (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 71B043A19E5; Mon, 12 Apr 2021 18:08:46 -0700 (PDT)
Received: by mail-io1-xd36.google.com with SMTP id x16so15428712iob.1; Mon, 12 Apr 2021 18:08:46 -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=e4I9ntUMQuABUiB7TSpq5pj3LnI7Hz2RjArQoOhavTo=; b=aF0TgjRMVsxHZbwvfQbHSjLSzXayETxOwlX8Z+OpgcoLhMjHiInKLkNUHetKg0E2JI WKiXT+5EU9e5N6qmIiLifgNGQjaq+YSD7pqArfxocG4M5Pn0CLCj24O5z8LpeZuMSX6/ EJrMlA1ZFfR+Z0RtrGEcq9SSDrUqBXoe/SlEEqoChv6DTz62eRnKCga1M7Lk2ywdk0KY iBG2fm99Xp83mGaqv1TxTkAiLI/2WLge7VoHkAsDf0O52HytvJnY98Q/J+iDq+66vhyv thLrDA1sE+jmyDHTyiRVp2gs6kTdHAh/RxKG0d1XDQWviac6G5IgDaGmIv4Cs5GvMYZo Ki2A==
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=e4I9ntUMQuABUiB7TSpq5pj3LnI7Hz2RjArQoOhavTo=; b=KgNI6b20+0MysbsQc8nErVNyCmCv3llwa3ZjW4QYNEC/x2gYX2LJIifdoacCrZ860m kKv/kr6UBofJpFn6p0hyWY0+JlJc7wo3U09DxFVXaI9lCdKmJHJesCDlFreOGOehxKCS +581GJ9FMgCCk6xdWZF45eTXF1QYGxHTuTsGSxAq025v2bK117i0WASH4syxa4i4//bB oRuNBVHaQnWqsvsofpGcmiW0yxJJidZ37DDURFOXaVXcLdyDBjT8Eojpqw7LDMY+c/h0 HTO7sqQU+6pShbV0GM8QguAlapNXM/IipNnKekDnKt38Gl0Bh8lGOG7XbQz05ZWYExr4 9vRw==
X-Gm-Message-State: AOAM53048WJTdtQIhUmcytWzfflGjXwsui82bqcLmZb0huPw7LhVY8vA uiKSrVY+1+Ygz2XQoGRTnicuDQZj/kseupOcJh4=
X-Google-Smtp-Source: ABdhPJx2XvYSPagDozyRmY1fJgc6nhJJxArMvKJaXpJnZBW1L46MYHJp8z1CXhfZHTfJHP12fbzYDMvLmLjrZV/1zLM=
X-Received: by 2002:a5d:8893:: with SMTP id d19mr5485333ioo.167.1618276123732; Mon, 12 Apr 2021 18:08:43 -0700 (PDT)
MIME-Version: 1.0
References: <161784748630.10496.1561945888518033066@ietfa.amsl.com> <CAF4+nEGkWP3FiFv2Zhzkv-BbQirv8osJ8qD2xrCUTmzhm1RdFA@mail.gmail.com> <4AC417C2-9668-4414-B7BC-EC069F05CD37@juniper.net>
In-Reply-To: <4AC417C2-9668-4414-B7BC-EC069F05CD37@juniper.net>
From: Donald Eastlake <d3e3e3@gmail.com>
Date: Mon, 12 Apr 2021 21:08:32 -0400
Message-ID: <CAF4+nEGhXvDYk6z79xCXp62=g_wunnBtyZDSgNYgLmdP2DbTiA@mail.gmail.com>
To: John Scudder <jgs@juniper.net>
Cc: The IESG <iesg@ietf.org>, "draft-ietf-bess-evpn-oam-req-frmwk@ietf.org" <draft-ietf-bess-evpn-oam-req-frmwk@ietf.org>, "bess-chairs@ietf.org" <bess-chairs@ietf.org>, "bess@ietf.org" <bess@ietf.org>, Matthew Bocci <matthew.bocci@nokia.com>
Content-Type: multipart/alternative; boundary="00000000000080f1ec05bfd045f5"
Archived-At: <https://mailarchive.ietf.org/arch/msg/bess/4F-kVzXPKEVpwI0PFRV1egWKc3U>
Subject: Re: [bess] John Scudder's Discuss on draft-ietf-bess-evpn-oam-req-frmwk-08: (with DISCUSS and COMMENT)
X-BeenThere: bess@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: BGP-Enabled ServiceS working group discussion list <bess.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/bess>, <mailto:bess-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/bess/>
List-Post: <mailto:bess@ietf.org>
List-Help: <mailto:bess-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/bess>, <mailto:bess-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 13 Apr 2021 01:08:57 -0000

Hi John,

I've posted -09 which should resolve your DISCUSS and COMMENTs.

Thanks,
Donald
===============================
 Donald E. Eastlake 3rd   +1-508-333-2270 (cell)
 2386 Panoramic Circle, Apopka, FL 32703 USA
 d3e3e3@gmail.com


On Mon, Apr 12, 2021 at 1:38 PM John Scudder <jgs@juniper.net> wrote:

> Thanks for hopping threads, I shoulda caught that last one. Your proposed
> change looks fine, I’ll remove my DISCUSS in anticipation of you issuing a
> new version. (One nit on your new text, “in order maximize” should be “in
> order to maximize”.)
>
> —John
>
> On Apr 12, 2021, at 1:03 PM, Donald Eastlake <d3e3e3@gmail.com> wrote:
>
>
> [External Email. Be cautious of content]
>
>
> Hi,
>
> On Wed, Apr 7, 2021 at 10:04 PM John Scudder via Datatracker <
> noreply@ietf.org> wrote:
> >
> > John Scudder has entered the following ballot position for
> > draft-ietf-bess-evpn-oam-req-frmwk-08: Discuss
> >
> > ...
> >
> > ----------------------------------------------------------------------
> > DISCUSS:
> > ----------------------------------------------------------------------
> >
> > Section 2.3:
> >
> >    EVPN Network OAM mechanisms MUST provide in-band monitoring
> >    capabilities. As such, OAM messages MUST be encoded so that they
> >    exhibit identical entropy characteristics to data traffic in order
> >    that they share the same fate.
> >
> > It’s not obvious to me what you mean by “identical entropy
> characteristics to
> > data traffic”. Surely, different flows may have different entropy
> > characteristics, so, *which* data traffic? Similarly, with which data
> traffic
> > are you saying the OAM messages must share fate?
>
> I guess when you changed your COMMENT to a DISCUSS it creates a new thread
> so I should reply here as I did to this when it was a COMMENT:
>
> How about something more like:
>
> EVPN Network OAM mechanisms MUST provide in-band monitoring capabilities.
> OAM messages SHOULD be encoded so that they exhibit similar entropy
> characteristics to data traffic in order maximize the fate sharing between
> OAM and data.
>
>
> > ----------------------------------------------------------------------
> > COMMENT:
> > ----------------------------------------------------------------------
> >
> > Thanks for the clear and readable document. I have one nit and one
> question.
> >
> > 1. Section 1, nit:
> >
> > “EVPN is an Layer 2” s/an/a/
>
> OK.
>
> Thanks,
> Donald
> ===============================
>  Donald E. Eastlake 3rd   +1-508-333-2270 (cell)
>  2386 Panoramic Circle, Apopka, FL 32703 USA
>  d3e3e3@gmail.com
>
>
>