Re: [Idr] WG LC for draft-ietf-idr-bgp-sendholdtimer-03 (3/23 to 4/12/2024) - Extended to 4/19/2024

William McCall <william.mccall@gmail.com> Tue, 16 April 2024 05:21 UTC

Return-Path: <william.mccall@gmail.com>
X-Original-To: idr@ietfa.amsl.com
Delivered-To: idr@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id DA71CC14F5F5 for <idr@ietfa.amsl.com>; Mon, 15 Apr 2024 22:21:07 -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, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-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=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 WgTr5f0XhiCP for <idr@ietfa.amsl.com>; Mon, 15 Apr 2024 22:21:04 -0700 (PDT)
Received: from mail-ej1-x632.google.com (mail-ej1-x632.google.com [IPv6:2a00:1450:4864:20::632]) (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 07C9AC14F61B for <idr@ietf.org>; Mon, 15 Apr 2024 22:21:03 -0700 (PDT)
Received: by mail-ej1-x632.google.com with SMTP id a640c23a62f3a-a523dad53e0so502095666b.1 for <idr@ietf.org>; Mon, 15 Apr 2024 22:21:03 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20230601; t=1713244862; x=1713849662; darn=ietf.org; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:from:to:cc:subject:date:message-id:reply-to; bh=YF0PX1wVc2K7XBz8t+2DoKYdDr4ekocf02hBBavcb9I=; b=Ah6z1mejGTf/Otfu/5w3QzthHdltr9c+G7rnswSh0odbiJS7tbvrO5e0qEwtMb7GSK vucHnAgqNRIi9jrK/ewRYlpjJIDaukILvJwvfYqDWJWey2ey/HOmHrE83B+8T/eD3icc F347YTDQ2+lL7K4HlJqG7a27/VLaoD8gV2+k31XC0P/xEnrvr6n1oODXPugdCB/4akoR Fw72EvoNMgh0Ckx1DO8z3Z547/UEilti2zmO/oVpUcZN9TZCVr7BZ7qbUlblKF7pti23 L0H7r1HPSExYFmc7RPHYu1hMxrBu5Hm0ror+bRcu9kU23gcrsJIB5UL/raQSij8hmIw4 3kgQ==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1713244862; x=1713849662; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:x-gm-message-state:from:to:cc:subject:date:message-id :reply-to; bh=YF0PX1wVc2K7XBz8t+2DoKYdDr4ekocf02hBBavcb9I=; b=HdYFBGNPKzCDO9xBQgjbGekSN2Yr7+c3CjcPQkZ+99tBUz920kFt11kNt9ePj1qYF+ qDzgwQq1Vl6cD3KMvTinSmJ7PC7FI6ztwrqKo5PibkJh5h81kRKcb1P1tJa/JWukKVCs dz84WKQgKxizIEVMttcQ6Oio57ZvMoSj91qVy2785VKWFloDZjZlMMeKFTA2/x4aJvQw Nqg5pgIQoBn3kmJVwONJYyd2+27If2IqoOfTbQoytQZ4T8bOwOjCXXV/xSz+DPtuE4GA 0q67HPQH/3f1VJC69WIUihF8w7LQyfv5FYkv1+Z1ZSvH5vWTYy9zhnUymx0oka8cgNcb AcGg==
X-Gm-Message-State: AOJu0YygmtCb7doHo1dmoe58afT1nUxz8kpTfk9PCQiMgo3bDf4dfBSa 8e5g8g8G9bkJt0M5EnNURi2DkL6ZS3YO6Et9gCz5CYTLK0eW01/ie/GCVavKmam5S/BsJo1EwWN XL/jXzgLlnbuLIpqEtN276CEgwKAURpGt
X-Google-Smtp-Source: AGHT+IELcT/ldNqE3R7Ib72XwFV3IBJwfoKlHlYkYQvq87mYBNfElmuKeIKmpr6DgIvlkn/oC2fdqMuOsZ0ePC3I2ok=
X-Received: by 2002:a17:906:b5b:b0:a51:abd8:8621 with SMTP id v27-20020a1709060b5b00b00a51abd88621mr1459734ejg.19.1713244861925; Mon, 15 Apr 2024 22:21:01 -0700 (PDT)
MIME-Version: 1.0
References: <DM6PR08MB48573863C5259A0DF98C335CB3042@DM6PR08MB4857.namprd08.prod.outlook.com> <CAOj+MMFe4C_G_T0OKvCJrk-RRyNuwRQZWa+UbvdLqCc9SrCu1A@mail.gmail.com>
In-Reply-To: <CAOj+MMFe4C_G_T0OKvCJrk-RRyNuwRQZWa+UbvdLqCc9SrCu1A@mail.gmail.com>
From: William McCall <william.mccall@gmail.com>
Date: Tue, 16 Apr 2024 05:20:49 +0000
Message-ID: <CA+eZshCC4C_VuFn_3c+yBN28=o=G2JYGkEkMbdeHEcD8-Wv1-g@mail.gmail.com>
To: Robert Raszuk <robert@raszuk.net>
Cc: "idr@ietf.org" <idr@ietf.org>
Content-Type: multipart/alternative; boundary="00000000000068920306162fe719"
Archived-At: <https://mailarchive.ietf.org/arch/msg/idr/sjxPjbWWGcJnP07WUGckF3CeFfc>
Subject: Re: [Idr] WG LC for draft-ietf-idr-bgp-sendholdtimer-03 (3/23 to 4/12/2024) - Extended to 4/19/2024
X-BeenThere: idr@ietf.org
X-Mailman-Version: 2.1.39
Precedence: list
List-Id: Inter-Domain Routing <idr.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/idr>, <mailto:idr-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/idr/>
List-Post: <mailto:idr@ietf.org>
List-Help: <mailto:idr-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/idr>, <mailto:idr-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 16 Apr 2024 05:21:08 -0000

On Mon, Apr 15, 2024 at 8:32 AM Robert Raszuk <robert@raszuk.net> wrote:

> Hi,
>
> Just for the record I do not support this WG LC.
>
> The proposed solution is not granular enough. While it is better
> than nothing, why to concentrate energy on a solution which may only react
> to stuck peer for hours (send buffer fill time when only keepalives are
> sent) and only cover subset of cases ?
>
> I am aware of at least one implementation of the TCP stack that is not
well architected to implement this as a feature. And it is widely used.

Today, draft-ietf-idr-bgp-sendholdtimer can be implemented on this stack
very easily and could see a reasonable solution to a problem that is proven
to have caused me problems in my network. Implementing TCP user timeout
logic would get a lot messier in terms of time-to-delivery. And I realize
that is not the overriding concern of IETF, but I can be selfish sometimes
:)

> We have proposed a TCP extension (which is already in the main kernel
> distro for a long time) which addresses the problem in a much more
> universal way.
>
> https://www.ietf.org/archive/id/draft-chen-idr-tcp-user-timeout-01.txt
>
> This draft proposes to use BGP KEEPALIVES or UPDATES to detect peer
> liveness while the proper way is to accomplish the same using TCP User
> Timeout.
>
> Of course some say - BGP folks do not always have freedom to access
> underlying OS TCP stack - that is true. But I would expect that the quality
> document going out of IDR WG would discuss all options so interested
> developer can choose (or check if his TCP stack already is fine) by for
> example merging draft-ietf-idr-bgp-sendholdtimer
> & draft-chen-idr-tcp-user-timeout
>

I support your draft as well as a separate doc. It's sensible, if a bit
more experimental than what is being proposed here. Mostly for the same
reasons that Mr. Haas has already brought up.

I don't support merging them. Too complicated and they're complimentary
processes that require some thought in a separate sense.

Would you be good with approaching it from two separate angles? I'd love to
work with you and Eric on it, if so.
-- 
William McCall