Re: [sfc] I-D Action: draft-ietf-sfc-nsh-ecn-support-10.txt

Donald Eastlake <d3e3e3@gmail.com> Fri, 30 September 2022 22:14 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 50CEFC14CF03 for <sfc@ietfa.amsl.com>; Fri, 30 Sep 2022 15:14:49 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.855
X-Spam-Level:
X-Spam-Status: No, score=-6.855 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_HI=-5, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01, URIBL_DBL_BLOCKED_OPENDNS=0.001, URIBL_ZEN_BLOCKED_OPENDNS=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 ([50.223.129.194]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id nFhtdR3sHmAm for <sfc@ietfa.amsl.com>; Fri, 30 Sep 2022 15:14:45 -0700 (PDT)
Received: from mail-lf1-x12a.google.com (mail-lf1-x12a.google.com [IPv6:2a00:1450:4864:20::12a]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 89115C14F742 for <sfc@ietf.org>; Fri, 30 Sep 2022 15:14:45 -0700 (PDT)
Received: by mail-lf1-x12a.google.com with SMTP id q14so2130183lfo.11 for <sfc@ietf.org>; Fri, 30 Sep 2022 15:14:45 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20210112; h=to:subject:message-id:date:from:in-reply-to:references:mime-version :from:to:cc:subject:date; bh=2mPWx4p39voeYJy9TLnRm8R3MOhiaTS1NgtIK9/co94=; b=XiAkrOYrRg8CgQzKzcBkQqNh8Vop0XCjVZAk71qxltKJoJI46cOXjrvnlUQte4Sdh1 c/kb93bb9P2HLjOQSbh6XGNhAKTSeKiprIpROICy2YP9IDzkyL8lWXAiysnBfXK233px mEwQGwbiTF9MZFjbvagCtCO0UTO6yXPl3GdxmzMv078vXxAvIGDE1BJAPzbl1zJ0Ysfy BrmDarId7TAGrsoxK/VSUbbmqV7BLfnEDmHz6PrAh7UGi5jVpzS5YsVZDrW9nvvzrCFA T2QqJZZhzJyfBNzf9rUCg78KPWcGvBd0MtP3684D6ap/0Q7LEaVys+Uk3UoZZiTjZGlx qMmA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=to:subject:message-id:date:from:in-reply-to:references:mime-version :x-gm-message-state:from:to:cc:subject:date; bh=2mPWx4p39voeYJy9TLnRm8R3MOhiaTS1NgtIK9/co94=; b=oQIwtd4YPLqKkU1sFSpb8nCh3s7xFRq6uUYt7bvH4tA/ei1PC5UyCH5L3fa8XaLpCi V4F0lAXYyg1VMi+VRYLMRx+rTstPGRtfcLBkxwDIEag6H+x8maN2ksifB/7vS3ZORoQD 2NorwezhOk5vNjHzG0j9wU4bM9Q9mPwj80cXrvHO9Bdu4ijjbMtM3NRtM8xI3fQHrPS1 CJJYjBGaig4rxlhnI+jkp4yB6hX4MpZ7fZwCG6upAXIEo/Gas1UWg82o3QsGLnz2EG1/ g/1RvRbOJDmn1pUKbkWv4cqyYGrycYaTMeKHS86e3cdUtYdrIBw8maiTGfMIeP0MdquQ T1jA==
X-Gm-Message-State: ACrzQf2ZteH8ct61r1/QSrk4G11nFyJISBZ+0/dByfLpUYGmPpm8C+Bc 3CDkDQZgt7xARSIiaOGunt/IoWVmiZjfr9ugRBX5+sLHWK0=
X-Google-Smtp-Source: AMsMyM7ogfQLlnIyvvgyiAF5M+hsxGOdzTf/1s8aZjBIh12heRK7/+9pfxX3wIlaqU5KscW5PHV3HeLk0JPpcFPjXXw=
X-Received: by 2002:a05:6512:3a8e:b0:4a2:f42:148 with SMTP id q14-20020a0565123a8e00b004a20f420148mr2291679lfu.343.1664576082788; Fri, 30 Sep 2022 15:14:42 -0700 (PDT)
MIME-Version: 1.0
References: <166457384721.57859.15162719761988881012@ietfa.amsl.com>
In-Reply-To: <166457384721.57859.15162719761988881012@ietfa.amsl.com>
From: Donald Eastlake <d3e3e3@gmail.com>
Date: Fri, 30 Sep 2022 18:14:31 -0400
Message-ID: <CAF4+nEHziAqWvP2gafaoTCu0ogGjxrn1w_cYC5iDuj-fMYppdQ@mail.gmail.com>
To: sfc@ietf.org
Content-Type: multipart/alternative; boundary="0000000000001dc5c305e9ec52fc"
Archived-At: <https://mailarchive.ietf.org/arch/msg/sfc/oSxJJBhb5d-CUnq1rl_8iqknr7Q>
Subject: Re: [sfc] I-D Action: draft-ietf-sfc-nsh-ecn-support-10.txt
X-BeenThere: sfc@ietf.org
X-Mailman-Version: 2.1.39
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: Fri, 30 Sep 2022 22:14:49 -0000

Hi,

I think this revision is a significant improvement and would appreciate it
if people looked at it.

Chairs: The IPFIX IE registry is Expert Review and the experts also form a
body of IE Doctors (see also RFC 7012). Should you ask for review of the
IPFIX IEs specified in this document and/or request allocation of code
points for them?

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


On Fri, Sep 30, 2022 at 5:38 PM <internet-drafts@ietf.org> wrote:

>
> A New Internet-Draft is available from the on-line Internet-Drafts
> directories.
> This draft is a work item of the Service Function Chaining WG of the IETF.
>
>         Title           : Explicit Congestion Notification (ECN) and
> Congestion Feedback Using the Network Service Header (NSH) and IPFIX
>         Authors         : Donald E. Eastlake
>                           Bob Briscoe
>                           Yizhou Li
>                           Andrew G. Malis
>                           Xinpeng Wei
>   Filename        : draft-ietf-sfc-nsh-ecn-support-10.txt
>   Pages           : 35
>   Date            : 2022-09-30
>
> Abstract:
>    Explicit Congestion Notification (ECN) allows a forwarding element to
>    notify downstream devices of the onset of congestion without having
>    to drop packets. Coupled with a means to feed information about
>    congestion back to upstream nodes, this can improve network
>    efficiency through better congestion control, frequently without
>    packet drops. This document specifies ECN and congestion feedback
>    support within a Service Function Chaining (SFC) enabled domain
>    through use of the Network Service Header (NSH, RFC 8300) and IP Flow
>    Information Export (IPFIX, RFC 7011) protocol.
>
>
>
> The IETF datatracker status page for this draft is:
> https://datatracker.ietf.org/doc/draft-ietf-sfc-nsh-ecn-support/
>
> There is also an htmlized version available at:
> https://datatracker.ietf.org/doc/html/draft-ietf-sfc-nsh-ecn-support-10
>
> A diff from the previous version is available at:
> https://www.ietf.org/rfcdiff?url2=draft-ietf-sfc-nsh-ecn-support-10
>
>
> Internet-Drafts are also available by rsync at rsync.ietf.org:
> :internet-drafts
>
>