[Sidrops] rfc8210 and rfc8210bis further question
Claudio Jeker <cjeker@diehard.n-r-g.com> Wed, 13 March 2024 12:45 UTC
Return-Path: <cjeker@diehard.n-r-g.com>
X-Original-To: sidrops@ietfa.amsl.com
Delivered-To: sidrops@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C55D5C14F74E for <sidrops@ietfa.amsl.com>; Wed, 13 Mar 2024 05:45:34 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.908
X-Spam-Level:
X-Spam-Status: No, score=-1.908 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_MSPIKE_H3=0.001, RCVD_IN_MSPIKE_WL=0.001, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01] 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 PolE80Bmeizi for <sidrops@ietfa.amsl.com>; Wed, 13 Mar 2024 05:45:34 -0700 (PDT)
Received: from diehard.n-r-g.com (diehard.n-r-g.com [62.48.3.9]) (using TLSv1.3 with cipher TLS_CHACHA20_POLY1305_SHA256 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA512) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id E9AF2C14F748 for <sidrops@ietf.org>; Wed, 13 Mar 2024 05:45:33 -0700 (PDT)
Received: (qmail 71729 invoked by uid 1000); 13 Mar 2024 12:45:29 -0000
Date: Wed, 13 Mar 2024 13:45:29 +0100
From: Claudio Jeker <cjeker@diehard.n-r-g.com>
To: sidrops@ietf.org
Message-ID: <ZfGf6WFVpApGtXpE@diehard.n-r-g.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Disposition: inline
Archived-At: <https://mailarchive.ietf.org/arch/msg/sidrops/KH4GCYVwh0BKPrqn4O40GY30eRs>
Subject: [Sidrops] rfc8210 and rfc8210bis further question
X-BeenThere: sidrops@ietf.org
X-Mailman-Version: 2.1.39
Precedence: list
List-Id: A list for the SIDR Operations WG <sidrops.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/sidrops>, <mailto:sidrops-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/sidrops/>
List-Post: <mailto:sidrops@ietf.org>
List-Help: <mailto:sidrops-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/sidrops>, <mailto:sidrops-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 13 Mar 2024 12:45:34 -0000
I'm looking at RTR again and realized that the protocol specification does not cover when the RTR timeouts should be reset to default values. At what point should a RTR router reset the protocol timing parameters back to the default values as specified in section 6? Should a fatal error also reset the protocol timing parameters? What are other implementations doing regarding these params? -- :wq Claudio
- [Sidrops] rfc8210 and rfc8210bis further question Claudio Jeker