Re: WGLC for draft-ietf-bfd-large-packets (Jeffrey Haas)
"Albert Fu (BLOOMBERG/ 120 PARK)" <afu14@bloomberg.net> Wed, 22 May 2024 03:58 UTC
Return-Path: <afu14@bloomberg.net>
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 D1305C20797B for <rtg-bfd@ietfa.amsl.com>; Tue, 21 May 2024 20:58:32 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.095
X-Spam-Level:
X-Spam-Status: No, score=-2.095 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIMWL_WL_HIGH=-0.001, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, HTML_MESSAGE=0.001, RCVD_IN_MSPIKE_H4=0.001, RCVD_IN_MSPIKE_WL=0.001, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001, 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=bloomberg.net
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 nOmGeoX9UKec for <rtg-bfd@ietfa.amsl.com>; Tue, 21 May 2024 20:58:28 -0700 (PDT)
Received: from mgnj15.bloomberg.net (mgnj15.bloomberg.net [69.191.244.237]) (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 A1F52C20C9B4 for <rtg-bfd@ietf.org>; Tue, 21 May 2024 20:58:27 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=bloomberg.net; l=9210; q=dns/txt; s=20220517; t=1716350308; x=1716436708; h=date:from:reply-to:to:mime-version:in-reply-to: message-id:subject:content-id; bh=aea59Qs+20Tb2nBy8RNi7u2xXWBNoIISgGiPefGx1/o=; b=dM+r27rP7Y7pre4cFd+i2+7HmQ12cy9i0mskx5gF7Oy5P5zKBCybqaEM 6KfuLbecUAy4s3seeMeyI6UvNrL+QG/8UKf0anzORtp1iO3o4eVIXb1yQ +04p4Z9q4PPCr1ejDdpIxqGu53Ks8Aj8qtk0P7YEAi3JRx2Cy2k56ApUs M4SConlNLJbSfjgs1/c38TuR5OMoG6NBUiWM9dH4+VOMyPGu1tWoHQ0yV 9jbRdG349/dTbawbklhk66brAGMkyxDpR0dUnb1TyNlwpLIV+oyZX+x+d Uv3GiCUT0VHyZirRI/OXTvx9zEgftv8oA3lDNHSW9shBvZUTh4GRx8hiR g==;
X-BB-Reception-Complete: 21 May 2024 23:58:26 -0400
X-IP-Listener: Outgoing Mail
X-IP-MID: 1267010010
Received: from omsg-pw-721.bloomberg.com (HELO omsg-pw-721) ([10.32.193.76]) by mgnj15.bloomberg.net with SMTP; 21 May 2024 23:58:26 -0400
X-BLP-INETSVC: version=BLP_APP_S_INETSVC_1.0.1; host=mgnj15:25; conid=730
Date: Wed, 22 May 2024 03:58:26 -0000
From: "Albert Fu (BLOOMBERG/ 120 PARK)" <afu14@bloomberg.net>
To: rtg-bfd@ietf.org
MIME-Version: 1.0
In-Reply-To: <171633651079.33237.16920075543676624389@ietfa.amsl.com>
Message-ID: <664D6D6200010F9A0C340001@message.bloomberg.net>
X-BLP-GUID: 664D6D6200010F9A0C3400010000
Subject: Re: WGLC for draft-ietf-bfd-large-packets (Jeffrey Haas)
Content-Type: multipart/alternative; boundary="BOUNDARY_664D6D6200010F9A0C340001_0_25608_omsg-pw-721"
Content-ID: <ID_664D6D6200010F9A0C340001_0_16867@omsg-pw-721>
Message-ID-Hash: S56MUUYORCSKZCBATLN6WIPQQJLVKJZ7
X-Message-ID-Hash: S56MUUYORCSKZCBATLN6WIPQQJLVKJZ7
X-MailFrom: afu14@bloomberg.net
X-Mailman-Rule-Misses: dmarc-mitigation; no-senders; approved; emergency; loop; banned-address; member-moderation; header-match-rtg-bfd.ietf.org-0; nonmember-moderation; administrivia; implicit-dest; max-recipients; max-size; news-moderation; no-subject; digests; suspicious-header
X-Mailman-Version: 3.3.9rc4
Precedence: list
Reply-To: Albert Fu <afu14@bloomberg.net>
List-Id: "RTG Area: Bidirectional Forwarding Detection" <rtg-bfd.ietf.org>
List-Archive: <https://mailarchive.ietf.org/arch/browse/rtg-bfd>
List-Help: <mailto:rtg-bfd-request@ietf.org?subject=help>
List-Owner: <mailto:rtg-bfd-owner@ietf.org>
List-Post: <mailto:rtg-bfd@ietf.org>
List-Subscribe: <mailto:rtg-bfd-join@ietf.org>
List-Unsubscribe: <mailto:rtg-bfd-leave@ietf.org>
Hi Les, > On May 21, 2024, at 2:40 AM, Les Ginsberg (ginsberg) > > Sooo…this was a real “blast-from-the-past” for me. > Over four years went by with no public updates – and in looking at the diffs between the latest version and V2 (which is where the discussion ended for me) it seems that not much has changed (albeit YANG section was introduced). > > I went back and reread the emails from years ago. It seems my concerns at the > time were addressed – largely by Section 4. Thanks for noting the delay - we wanted to wait till we have a vendor implementation before requesting for adoption. Juniper has indeed implemented this feature starting in JUNOS 23.2: https://www.juniper.net/documentation/us/en/software/junos/release-notes/23.2/junos-release-notes-23.2r1/topics/new-features/feature-descriptions/high-availability-13.html Example of config to test padded size of 1512 bytes = 1500 IP_Payload + 3*MPLS_Headers = 1512 = 1484 (this is Juniper BFD pdu-size) + 28 (IP+UDP Hdrs) set protocols ospf area 0.0.0.0 interface et-0/0/4.0 bfd-liveness-detection minimum-interval 150 set protocols ospf area 0.0.0.0 interface et-0/0/4.0 bfd-liveness-detection multiplier 3 set protocols ospf area 0.0.0.0 interface et-0/0/4.0 bfd-liveness-detection pdu-size 1484 set protocols ospf area 0.0.0.0 interface et-0/0/4.0 strict-bfd We are still seeing "MTU" issue from time to time in our network (e.g. just a few weeks ago, we experienced this issue with one of our international circuits in India). We plan to deploy this feature on our P2P OSPF and eBGP links, which are predominantly where we enable BFD for fast failure detection. Currently, we use periodic pings to detect and alarm the "mtu" issue, which is not ideal. With the BFD Large Packet feature, we will be able to instantly detect the issue and divert traffic to working circuits. Thanks Albert Fu Bloomberg PS: Later JUNOS version has better scaling property.
- Re: WGLC for draft-ietf-bfd-large-packets (Jeffre… Albert Fu (BLOOMBERG/ 120 PARK)