Re: [sfc] The SFC WG has placed draft-eastlake-sfc-nsh-ecn-support in state "Candidate for WG Adoption"

Tal Mizrahi <tal.mizrahi.phd@gmail.com> Mon, 07 January 2019 07:57 UTC

Return-Path: <tal.mizrahi.phd@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 A5765130E8A; Sun, 6 Jan 2019 23:57:15 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.999
X-Spam-Level:
X-Spam-Status: No, score=-1.999 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] 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 4joOINOerjCa; Sun, 6 Jan 2019 23:57:13 -0800 (PST)
Received: from mail-qt1-x830.google.com (mail-qt1-x830.google.com [IPv6:2607:f8b0:4864:20::830]) (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 33546130E68; Sun, 6 Jan 2019 23:57:13 -0800 (PST)
Received: by mail-qt1-x830.google.com with SMTP id e5so46714315qtr.12; Sun, 06 Jan 2019 23:57:13 -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 :cc; bh=hR7g9LmMXbK7FBMfb/q9MR4ZtEJGC0J52TqjFIKEs5s=; b=Nk7n5eBzJEToEqyiPmQc3xeGqdnAehGoE3InWnGaWTmUnYoPS1PBe7YgmB4A3yEcPN v5IEKGOjwrvPbCtpz8OUfKPrntmI2IbvwRjVJPaICvK09Z0G6zPPIMEHG8EOzDhG5wdE hO6gYIeapX+RQCB269hbOP4zHzN7/yIvN+nx9YDQcwZvbiriKzqFN/fxAi3TRNh+1sJg HM66UQgVzBBMVEiiFKkfpxMPswuDC5+/JNnufON9JgsA31HZuHUGnsm511syoRdwW6vh 5nWXq54qgrMKM2MJUiH+vqL8qAVczpWPTrnyA7uyVk2OtZQkHME6nWm5VkOC34JrruYC nCUA==
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=hR7g9LmMXbK7FBMfb/q9MR4ZtEJGC0J52TqjFIKEs5s=; b=jikt0gcgAL20W0pLTzFLsm9P5+qGh8WbIn5zpg0rcVXWiF+Ry2Uf54Hzfoq0qSS/4Z PSK/xpbvAH5JWkhaj2skmk4YYYTpoM1y8uB4PGvBCEUa97x3DNHI1kiBoRTUAChUUm0s ld0G9WKdL/XsOAYn3iQBaQtIOJt3WRGW9Rn8SFzH/76Xx0MrJoljLP09psNAx5/xrPvN Cq7mr8edtwIZ9jKae7w1hiV12ODBIyeVyJv2eDQY42oTpgF5JL3ZK608iRgRYNcKC4UA oKXsEkZsbsX0iypZvMMceHuIFbCLPza0wp+hKw3dpYrIjfSWhMXFLc6KWYUHS9/KPMEM 8f+w==
X-Gm-Message-State: AA+aEWa957yQaG8nkgkrrf5fLLvKYDqYfnS5VFTDM3GFlFjTeK8P1DUt 1S2EQN1EvecGFVEERWVI4+kLWAcIGhpjCP3lBbySpoSyLWI=
X-Google-Smtp-Source: AFSGD/Xc87Spn9uETVEFwuVgzW5nI90psUEmuvt8ulYp0TOdnJBMEIy0AX8gIgIj3UmJVTZVQvh5nus0spNMrwjFgTI=
X-Received: by 2002:aed:33e3:: with SMTP id v90mr58070840qtd.261.1546847832109; Sun, 06 Jan 2019 23:57:12 -0800 (PST)
MIME-Version: 1.0
References: <154649225579.32607.12231566034033496144.idtracker@ietfa.amsl.com>
In-Reply-To: <154649225579.32607.12231566034033496144.idtracker@ietfa.amsl.com>
From: Tal Mizrahi <tal.mizrahi.phd@gmail.com>
Date: Mon, 07 Jan 2019 09:57:01 +0200
Message-ID: <CABUE3XmrmTK9EJLGD=Zz1ANSAqja-avTuoAGgNoAcALqAVVOrA@mail.gmail.com>
To: IETF Secretariat <ietf-secretariat-reply@ietf.org>
Cc: sfc-chairs@ietf.org, draft-eastlake-sfc-nsh-ecn-support@ietf.org, sfc@ietf.org
Content-Type: multipart/alternative; boundary="0000000000008df8dd057ed9933c"
Archived-At: <https://mailarchive.ietf.org/arch/msg/sfc/o92nF9FoaIJM5fseUrC3CbzvLS0>
Subject: Re: [sfc] The SFC WG has placed draft-eastlake-sfc-nsh-ecn-support in state "Candidate for WG Adoption"
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: Mon, 07 Jan 2019 07:57:16 -0000

Hi,

I reviewed the draft, and I believe it is worth pursuing in the working
group.

Comments:

- Section 1.3 / Section 4: these sections discuss how the ingress node
(classifier) may react to the congestion. However, it seems that there may
be a conflict if the egress node both propagates the ECN to the destination
AND sends a congestion feedback to the ingress node. In this case traffic
may be throttled by two nodes (traffic source and NSH classifier). It would
be helpful if the draft clarifies whether these two behaviors are mutually
exclusive, or how they coexist.

- The draft implies that in a network that uses ECN-in-NSH the Ingress and
Egress nodes must be ECN aware, while the SFFs and SFs may be ECN unaware,
allowing interoperability with older SFF/SF nodes. I would suggest to state
this explicitly in the introduction.

- "It MAY instead be set to ECT(1) if the NSH domain supports the
experimental L4S capability [RFC8311], [ecnL4S]."
  This sentence is confusing from an implementer's perspective. Does the
"MAY" here allow interoperability between the two approaches (RFC3168/
RFC8311)? Please clarify in the draft whether ECN-in-NSH-aware nodes are
expected to be implemented as defined in [RFC3168] or as in [RFC8311], or a
combination of both.

Cheers,
Tal.

On Thu, Jan 3, 2019 at 7:11 AM IETF Secretariat <
ietf-secretariat-reply@ietf.org> wrote:

>
> The SFC WG has placed draft-eastlake-sfc-nsh-ecn-support in state
> Candidate for WG Adoption (entered by Joel Halpern)
>
> The document is available at
> https://datatracker.ietf.org/doc/draft-eastlake-sfc-nsh-ecn-support/
>
> Comment:
> This starts the WG call for adoption of this draft.
> Please respond to the list, indicating support for this as a work item of
> the
> working group with this document as the basis for the work, or objection to
> the working group adopting this item as a working group draft.
>
> The authors should confirm to the chairs and WG secretary that all IPR
> known
> to them relevant to this draft has been disclosed.
>
> The working group adoption call will last 2 weeks, ending at the end of the
> day on Thursday, January 17 2019 COB somewhere.
>
> Thank you,
> Joel
>