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

Donald Eastlake <d3e3e3@gmail.com> Tue, 08 January 2019 21:43 UTC

Return-Path: <d3e3e3@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 6263B13119A; Tue, 8 Jan 2019 13:43:51 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.749
X-Spam-Level:
X-Spam-Status: No, score=-1.749 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_ENVFROM_END_DIGIT=0.25, FREEMAIL_FROM=0.001, RCVD_IN_DNSWL_NONE=-0.0001, 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 CQl2FErUb52P; Tue, 8 Jan 2019 13:43:50 -0800 (PST)
Received: from mail-io1-xd30.google.com (mail-io1-xd30.google.com [IPv6:2607:f8b0:4864:20::d30]) (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 0F63F131199; Tue, 8 Jan 2019 13:43:50 -0800 (PST)
Received: by mail-io1-xd30.google.com with SMTP id m19so4388143ioh.3; Tue, 08 Jan 2019 13:43:49 -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:content-transfer-encoding; bh=ym+lGuhPtceZic2HeJnwOJ6hBgbeVdepGc3ij3P351o=; b=arGyM63FVXvtvXvnJKZYkt2qZSSG27ZmMS3C7l/Ahheo4Vtw1wYxi7DkSAPmI82fIb Ts2YxKWG2o1z238OsXCrj8fVKzISxKI53wYvHP0Va6dArZ1FSe1PdnSZCmRneRUqZf2I 59XzF5rkXsJzUQln1syCNiowTfK+wzeoyh0V1mfopXc3oVs135Dkjr5dHH3dVptJDIRY LVv/J1TulrHund/joOqJkus4whlTbUr3AsQxsj5zMc+duQdq0jqtW1AunRT17FbyFXEF an3Kn5sQ3aDV0Sv7ptKjFuNZr75eDoQbI1+nstxZMVDAnjhrl/xLxgnoSkyOYp+LykiU 9J0w==
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:content-transfer-encoding; bh=ym+lGuhPtceZic2HeJnwOJ6hBgbeVdepGc3ij3P351o=; b=YwjehcRlyULYB3DCFFGxK4uq9j4V9SPeeXvE5jvXfdA2GRB86zIm36mgf8vhTw05qc kaLs4L01rSS2FkuETF23FNjgHSGIb6Gp4xOcEVDcoSbtpEWV6+QV0ke3RqKou0Te5f0x IWF4k62to/SnH+a6mEG+BKMGDVtbK6EmKNqgvOgk/lPFxyl7sWFmZ3WoLhs/upU8Uo2N PlydLDF7WUmse/ayVWu624BO1gQGZGhxYrgsPZz0Ll5/SrOgoGPkwxukPpEMAlG2e72t spfn3TXo3/fwBDNAmy26TTuFnNvgCn5TtFY3X8GIX7t6Vr0NEaKxRJ1RrTnUn3QTxPc5 axrA==
X-Gm-Message-State: AJcUukfXix/HRUlvrwB8nN1DpjGOvpH8qMbNWCKxU4tk9wrmU4+QR2o/ 5uJjjujk6J+0mQ2AJcgtRIf4MBBKZrFue1dSTzDoR21GKBc=
X-Google-Smtp-Source: ALg8bN6ZGna4jp5MwMqwMKByu1sugQhpQpjI5/59fVlWbtXiHRjJBuLzF3Ye/du/6DZksweMiTF1QC9mdoa6IXBdDqc=
X-Received: by 2002:a5d:88ce:: with SMTP id i14mr2481164iol.66.1546983829191; Tue, 08 Jan 2019 13:43:49 -0800 (PST)
MIME-Version: 1.0
References: <154649225579.32607.12231566034033496144.idtracker@ietfa.amsl.com> <CABUE3XmrmTK9EJLGD=Zz1ANSAqja-avTuoAGgNoAcALqAVVOrA@mail.gmail.com>
In-Reply-To: <CABUE3XmrmTK9EJLGD=Zz1ANSAqja-avTuoAGgNoAcALqAVVOrA@mail.gmail.com>
From: Donald Eastlake <d3e3e3@gmail.com>
Date: Tue, 08 Jan 2019 16:43:37 -0500
Message-ID: <CAF4+nEHFcEa18b0zJ+myqo=GmzdRB=iycH5vXAU=kK9A-FjPyA@mail.gmail.com>
To: Tal Mizrahi <tal.mizrahi.phd@gmail.com>
Cc: IETF Secretariat <ietf-secretariat-reply@ietf.org>, sfc-chairs@ietf.org, draft-eastlake-sfc-nsh-ecn-support@ietf.org, sfc@ietf.org
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
Archived-At: <https://mailarchive.ietf.org/arch/msg/sfc/c_7fS8zGY9Rkc5wv-CPwySRC5bU>
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: Tue, 08 Jan 2019 21:43:51 -0000

Hi Tal,

On Mon, Jan 7, 2019 at 2:57 AM Tal Mizrahi <tal.mizrahi.phd@gmail.com> wrote:
>
> Hi,
>
> I reviewed the draft, and I believe it is worth pursuing in the working group.

Thanks for the support.

> 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.

That is a reasonable consideration and the draft should probably talk
about it. I think some actions by the NSH classifier could cause
problems but there are other NSH classifier actions that would be OK.

> - 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.

OK.

> - "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.

I agree we need to clarify that.

Thanks,
Donald
===============================
 Donald E. Eastlake 3rd   +1-508-333-2270 (cell)
 1424 Pro Shop Court, Davenport, FL 33896 USA
 d3e3e3@gmail.com

> 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