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

heasley <heas@shrubbery.net> Fri, 19 April 2024 11:48 UTC

Return-Path: <heas@shrubbery.net>
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 AC356C14F6B4 for <idr@ietfa.amsl.com>; Fri, 19 Apr 2024 04:48:13 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.899
X-Spam-Level:
X-Spam-Status: No, score=-6.899 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_HI=-5, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-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 vwVKKsL6BsBO for <idr@ietfa.amsl.com>; Fri, 19 Apr 2024 04:48:09 -0700 (PDT)
Received: from sea.shrubbery.net (sea.shrubbery.net [129.250.47.99]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 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 23045C14F6B5 for <idr@ietf.org>; Fri, 19 Apr 2024 04:48:08 -0700 (PDT)
Received: by sea.shrubbery.net (Postfix, from userid 7053) id 58D0426562C; Fri, 19 Apr 2024 11:48:08 +0000 (UTC)
Date: Fri, 19 Apr 2024 11:48:08 +0000
From: heasley <heas@shrubbery.net>
To: tom petch <ietfc@btconnect.com>
Cc: Susan Hares <shares@ndzh.com>, "idr@ietf.org" <idr@ietf.org>
Message-ID: <ZiJZ-Lfd9kmG3LVC@shrubbery.net>
References: <DM6PR08MB48573863C5259A0DF98C335CB3042@DM6PR08MB4857.namprd08.prod.outlook.com> <AM4PR07MB314043BCF3BC57892534695BA00D2@AM4PR07MB3140.eurprd07.prod.outlook.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Disposition: inline
In-Reply-To: <AM4PR07MB314043BCF3BC57892534695BA00D2@AM4PR07MB3140.eurprd07.prod.outlook.com>
X-PGPkey: http://www.shrubbery.net/~heas/public-key.asc
X-note: live free, or die!
X-homer: i just want to have a beer while i am caring.
X-Claimation: an engineer needs a manager like a fish needs a bicycle
X-reality: only YOU can put an end to the embarrassment that is Tom Cruise
Archived-At: <https://mailarchive.ietf.org/arch/msg/idr/GfL4RroDGFkmfRctEuz5wv_vB5c>
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: Fri, 19 Apr 2024 11:48:13 -0000

Fri, Apr 19, 2024 at 09:51:36AM +0000, tom petch:
> I think that the draft underestimates substantially the changes needed to the base specification of the FSM.  The idea is fine but the details are lacking and that may lead to divergent implementations of what is a rather important protocol.

Aren't those details which are or can be resolved after adoption?  Including
the possibility of abandonment.