Re: BFD for large packets

xiao.min2@zte.com.cn Mon, 29 January 2024 06:27 UTC

Return-Path: <xiao.min2@zte.com.cn>
X-Original-To: rtg-bfd@ietfa.amsl.com
Delivered-To: rtg-bfd@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 3413BC14F605 for <rtg-bfd@ietfa.amsl.com>; Sun, 28 Jan 2024 22:27:21 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.603
X-Spam-Level:
X-Spam-Status: No, score=-2.603 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, RCVD_IN_MSPIKE_H5=0.001, RCVD_IN_MSPIKE_WL=0.001, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01, UNPARSEABLE_RELAY=0.001, URIBL_DBL_BLOCKED_OPENDNS=0.001, URIBL_ZEN_BLOCKED_OPENDNS=0.001] autolearn=ham autolearn_force=no
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 kfxEIEgvlvNJ for <rtg-bfd@ietfa.amsl.com>; Sun, 28 Jan 2024 22:27:19 -0800 (PST)
Received: from mxhk.zte.com.cn (mxhk.zte.com.cn [63.216.63.40]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 7D146C14F604 for <rtg-bfd@ietf.org>; Sun, 28 Jan 2024 22:27:18 -0800 (PST)
Received: from mse-fl1.zte.com.cn (unknown [10.5.228.132]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mxhk.zte.com.cn (FangMail) with ESMTPS id 4TNdcy1NQLz8XrRC; Mon, 29 Jan 2024 14:27:14 +0800 (CST)
Received: from njy2app04.zte.com.cn ([10.40.12.64]) by mse-fl1.zte.com.cn with SMTP id 40T6Qqta015156; Mon, 29 Jan 2024 14:26:52 +0800 (+08) (envelope-from xiao.min2@zte.com.cn)
Received: from mapi (njy2app03[null]) by mapi (Zmail) with MAPI id mid201; Mon, 29 Jan 2024 14:26:54 +0800 (CST)
Date: Mon, 29 Jan 2024 14:26:54 +0800
X-Zmail-TransId: 2afb65b7452effffffff9b9-fd0d3
X-Mailer: Zmail v1.0
Message-ID: <202401291426544994664@zte.com.cn>
In-Reply-To: <20240128215631.GC11839@pfrc.org>
References: 20240128215631.GC11839@pfrc.org
Mime-Version: 1.0
From: xiao.min2@zte.com.cn
To: jhaas@pfrc.org
Cc: rtg-bfd@ietf.org
Subject: Re: BFD for large packets
Content-Type: multipart/mixed; boundary="=====_001_next====="
X-MAIL: mse-fl1.zte.com.cn 40T6Qqta015156
X-Fangmail-Gw-Spam-Type: 0
X-Fangmail-Anti-Spam-Filtered: true
X-Fangmail-MID-QID: 65B74542.001/4TNdcy1NQLz8XrRC
Archived-At: <https://mailarchive.ietf.org/arch/msg/rtg-bfd/aNbhl35ZOtd9RNbQs35KCWyXRrM>
X-BeenThere: rtg-bfd@ietf.org
X-Mailman-Version: 2.1.39
Precedence: list
List-Id: "RTG Area: Bidirectional Forwarding Detection DT" <rtg-bfd.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/rtg-bfd>, <mailto:rtg-bfd-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/rtg-bfd/>
List-Post: <mailto:rtg-bfd@ietf.org>
List-Help: <mailto:rtg-bfd-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/rtg-bfd>, <mailto:rtg-bfd-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 29 Jan 2024 06:27:21 -0000

Hi Jeff,

Thanks for resuming your work on this document, which seems to me a useful one.
Glad to work with you and Albert on incorporating draft-xiao-bfd-padding-alteration-00 into draft-ietf-bfd-large-packets if applicable.
Best Regards,
Xiao Min

Original


From: JeffreyHaas <jhaas@pfrc.org>
To: rtg-bfd@ietf.org <rtg-bfd@ietf.org>;
Cc: 肖敏10093570;
Date: 2024年01月29日 05:56
Subject: BFD for large packets

[Speaking as an individual contributor.]
 
As part of trying to push BFD WG work to conclusion, I've re-issued BFD for
large packets.  Our last big push on the document was back in 2019,
including a first and not conclusive pass toward Working Group Last Call.
 
Since then, Juniper has done an initial implementation of the draft.  Les
might find it vindicating that part of the learnings from that
implementation were that naive implementations have interesting scaling
headaches.  That said, the outcome of that work were mostly the same as the
rest of the use of BFD: you have to work based on the scaling of your
platform.  Optimization work is under way to push our scaling up, but those  
implementation details rather than something that impacts the draft text.
 
There are two lingering items Albert and I will be addressing in the near
term, both tracked in the github I did the original work in[1]:
 
1. We should add YANG support for this feature.
2. There was a request from Xiao Min to consider whether work in his padding
   alteration proposal[2] was appropriate to directly incorporate in the large
   packets draft.  Albert and I will be considering what such a fit would
   look like and work with Xiao Min on the text.
 
   Reshad had indicated back in 2019 that incorporating such changes would
   likely require polled support from the Working Group.  We'll thus do some
   text for WG review prior to including it in future versions of the draft
   directly.
 
-- Jeff
 
[1] https://github.com/jhaas-pfrc/bfd-large-packets
[2] https://datatracker.ietf.org/doc/html/draft-xiao-bfd-padding-alteration-00
 
----- Forwarded message from internet-drafts@ietf.org -----
 
Date: Sun, 28 Jan 2024 13:33:51 -0800
From: internet-drafts@ietf.org
To: i-d-announce@ietf.org
Cc: rtg-bfd@ietf.org
Subject: I-D Action: draft-ietf-bfd-large-packets-03.txt
 
Internet-Draft draft-ietf-bfd-large-packets-03.txt is now available. It is a
work item of the Bidirectional Forwarding Detection (BFD) WG of the IETF.
 
   Title:   BFD Encapsulated in Large Packets
   Authors: Jeffrey Haas
            Albert Fu
   Name:    draft-ietf-bfd-large-packets-03.txt
   Pages:   7
   Dates:   2024-01-28
 
Abstract:
 
   The Bidirectional Forwarding Detection (BFD) protocol is commonly
   used to verify connectivity between two systems.  BFD packets are
   typically very small.  It is desirable in some circumstances to know
   that not only is the path between two systems reachable, but also
   that it is capable of carrying a payload of a particular size.  This
   document discusses thoughts on how to implement such a mechanism
   using BFD in Asynchronous mode.
 
The IETF datatracker status page for this Internet-Draft is:
https://datatracker.ietf.org/doc/draft-ietf-bfd-large-packets/
 
There is also an HTML version available at:
https://www.ietf.org/archive/id/draft-ietf-bfd-large-packets-03.html
 
A diff from the previous version is available at:
https://author-tools.ietf.org/iddiff?url2=draft-ietf-bfd-large-packets-03
 
Internet-Drafts are also available by rsync at:
rsync.ietf.org::internet-drafts
 
 
----- End forwarded message -----