Re: [sfc] I-D Action: draft-ietf-sfc-nsh-ecn-support-06.txt
"Joel M. Halpern" <jmh@joelhalpern.com> Mon, 13 September 2021 21:08 UTC
Return-Path: <jmh@joelhalpern.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 A8D193A0E1E; Mon, 13 Sep 2021 14:08:07 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.099
X-Spam-Level:
X-Spam-Status: No, score=-2.099 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, NICE_REPLY_A=-0.001, RCVD_IN_MSPIKE_H3=0.001, RCVD_IN_MSPIKE_WL=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=joelhalpern.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 GQUM0G96a6v8; Mon, 13 Sep 2021 14:08:03 -0700 (PDT)
Received: from mailb2.tigertech.net (mailb2.tigertech.net [208.80.4.154]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 06BDF3A0E1A; Mon, 13 Sep 2021 14:08:02 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by mailb2.tigertech.net (Postfix) with ESMTP id 4H7fFt4gpxz1nspm; Mon, 13 Sep 2021 14:08:02 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=joelhalpern.com; s=2.tigertech; t=1631567282; bh=fxPQQhCdRozif7IIBU8RVlOvZYUX+ox8PUpD3ArQKHw=; h=Subject:To:Cc:References:From:Date:In-Reply-To:From; b=JJ5M6gHsGVEmy8hVmZTbhAeVlsrQmNnxsHDRPOh5LW2jZkqmKyAtjTx9cXs4piTQP 09f/MB5HaJhWUbDO2jJK2vwdtaHR7eeiNOLgKdlM6e8CsgpUthHKlQSmmooTZmaXRK eR54MBBKkr51k2yV1UoHA07A19u692bNoTwS9a00=
X-Quarantine-ID: <b0d-d7jqKUqn>
X-Virus-Scanned: Debian amavisd-new at b2.tigertech.net
Received: from [192.168.23.64] (50-233-136-230-static.hfc.comcastbusiness.net [50.233.136.230]) (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 mailb2.tigertech.net (Postfix) with ESMTPSA id 4H7fFs5X9Hz1nsSp; Mon, 13 Sep 2021 14:08:01 -0700 (PDT)
To: Donald Eastlake <d3e3e3@gmail.com>, sfc@ietf.org
Cc: draft-ietf-sfc-nsh-ecn-support@ietf.org
References: <163156351922.30301.16195659550273547515@ietfa.amsl.com> <CAF4+nEE3rMHd64bD9ZCtDJp9z=vep0s8Tes0_u1O0F5wD4zGFQ@mail.gmail.com>
From: "Joel M. Halpern" <jmh@joelhalpern.com>
Message-ID: <82a68b38-5e92-2b7e-2326-bcb026eeed58@joelhalpern.com>
Date: Mon, 13 Sep 2021 17:07:59 -0400
User-Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:78.0) Gecko/20100101 Thunderbird/78.14.0
MIME-Version: 1.0
In-Reply-To: <CAF4+nEE3rMHd64bD9ZCtDJp9z=vep0s8Tes0_u1O0F5wD4zGFQ@mail.gmail.com>
Content-Type: text/plain; charset="utf-8"; format="flowed"
Content-Language: en-US
Content-Transfer-Encoding: 7bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/sfc/jNOFwy8jTb7ebSXv5RxUnwGE4Yc>
Subject: Re: [sfc] I-D Action: draft-ietf-sfc-nsh-ecn-support-06.txt
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, 13 Sep 2021 21:08:08 -0000
While such a facility (to inform about packet changes) has understandable value, I tend to doubt the likelihood of it being used. It seeems an unlikely upgrade for a SF builder to bother implementing, since it is likely to be significant effort. And existing SF (including all those behind proxies) will not support it. Yours, Joel On 9/13/2021 4:56 PM, Donald Eastlake wrote: > This revision has minor wording improvements. > > To my mind there is one substantial issue with this draft: What to do > about SFs that add or remove packets from a flow or lengthen or > shorten such packets. If this is ignored, the document is much less > useful for such flows. The simplest solution seems to be that such SFs > should optionally signal forward in separate packets the changes they > have made, of this sort, to flows. I plan to look into adding such a > facility. > > Thanks, > Donald > =============================== > Donald E. Eastlake 3rd +1-508-333-2270 (cell) > 2386 Panoramic Circle, Apopka, FL 32703 USA > d3e3e3@gmail.com > > On Mon, Sep 13, 2021 at 4:06 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-06.txt >> Pages : 33 >> Date : 2021-09-13 >> >> 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) architecture domain >> through use of the Network Service Header (NSH, RFC 8300) and IP Flow >> Information Export (IPFIX, RFC 7011). >> >> >> >> 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-06 >> >> A diff from the previous version is available at: >> https://www.ietf.org/rfcdiff?url2=draft-ietf-sfc-nsh-ecn-support-06 >> >> >> Internet-Drafts are also available by anonymous FTP at: >> ftp://ftp.ietf.org/internet-drafts/ >> >> >> _______________________________________________ >> sfc mailing list >> sfc@ietf.org >> https://www.ietf.org/mailman/listinfo/sfc > > _______________________________________________ > sfc mailing list > sfc@ietf.org > https://www.ietf.org/mailman/listinfo/sfc >
- [sfc] I-D Action: draft-ietf-sfc-nsh-ecn-support-… internet-drafts
- Re: [sfc] I-D Action: draft-ietf-sfc-nsh-ecn-supp… Donald Eastlake
- Re: [sfc] I-D Action: draft-ietf-sfc-nsh-ecn-supp… Joel M. Halpern
- Re: [sfc] I-D Action: draft-ietf-sfc-nsh-ecn-supp… Donald Eastlake