Re: [radext] Watchdog behaviour (was: Confirmation of discussions on RADIUS/(D)TLS at IETF117)
Alexander Clouter <alex+ietf@coremem.com> Wed, 02 August 2023 18:21 UTC
Return-Path: <alex+ietf@coremem.com>
X-Original-To: radext@ietfa.amsl.com
Delivered-To: radext@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id DB299C14CEFF for <radext@ietfa.amsl.com>; Wed, 2 Aug 2023 11:21:41 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.104
X-Spam-Level:
X-Spam-Status: No, score=-2.104 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, RCVD_IN_DNSWL_BLOCKED=0.001, RCVD_IN_MSPIKE_H5=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, 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=coremem.com header.b="YYDFSWbG"; dkim=pass (2048-bit key) header.d=messagingengine.com header.b="Y4EyQIfo"
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 2aHSvjQiLIWZ for <radext@ietfa.amsl.com>; Wed, 2 Aug 2023 11:21:37 -0700 (PDT)
Received: from wout1-smtp.messagingengine.com (wout1-smtp.messagingengine.com [64.147.123.24]) (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 376B2C151707 for <radext@ietf.org>; Wed, 2 Aug 2023 11:21:20 -0700 (PDT)
Received: from compute5.internal (compute5.nyi.internal [10.202.2.45]) by mailout.west.internal (Postfix) with ESMTP id 8349432001BB for <radext@ietf.org>; Wed, 2 Aug 2023 14:21:19 -0400 (EDT)
Received: from imap46 ([10.202.2.96]) by compute5.internal (MEProxy); Wed, 02 Aug 2023 14:21:19 -0400
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=coremem.com; h= cc:content-type:content-type:date:date:from:from:in-reply-to :in-reply-to:message-id:mime-version:references:reply-to:sender :subject:subject:to:to; s=fm2; t=1691000479; x=1691086879; bh=PR 1TMY+SZhmsBhQW3aiwfhutFHpDg1UHQrdNKTxpBlw=; b=YYDFSWbGPpdMLEu3+D WNThtfbek4QY/RQF0RC2Om1GBTL6DcwemMe0JyACLTaTKwtDzJzEk2RLBcDG+RVe Z5kYwLH0PSOactj+bJaAyIoHXLCw0Mae5mgvsL3ohYv9NUM339D8fZSMr7jRjn6Z Y4pkHraRs/bIAIFEOJmjeR0yx5AQFTW1qgXvl5em/eomckY8j/uu01Ctfm1TzXP7 ecgiS/odnmHK1j9Fme/mR63+HcI+r71Du/3wcItWuZ5G6ewvshii3rpVFcyXo0N9 stKJ3/Z0t4Y3GnJlNuONw3ramZ0JL3BgVLRk/6npD2kBpzLex6rDEX2kz0d6BI7x s5Tw==
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=cc:content-type:content-type:date:date :feedback-id:feedback-id:from:from:in-reply-to:in-reply-to :message-id:mime-version:references:reply-to:sender:subject :subject:to:to:x-me-proxy:x-me-proxy:x-me-sender:x-me-sender :x-sasl-enc; s=fm3; t=1691000479; x=1691086879; bh=PR1TMY+SZhmsB hQW3aiwfhutFHpDg1UHQrdNKTxpBlw=; b=Y4EyQIfo91xiB7njKtHHUvOof048i 6TNQcL7M9qN+kaumoW+b1JJ0UR/tT5hzbIBSwlk5G+O5r+ONTxRPRLDeejSvzdXg tfo1iS3UBWWiqIuWaDkpnA5jhplUpGapLXF7J9Ydjc5zk1d9Q3pt7xxB7wf3YRkM NbcQOvmKCawJyHyq9CctsPl5uG8jpwv4ghfSQWqyn+Gjv8OqGISkLMR/R5FnxIeO HqeeNiOm32GdEN09nKMYGOS/JSBGH4ux8MG+MfqjllzerGtI4ONxBjG6FNzz/+ub epRO4hcgX45/KZzFPb3yX8Bdnk2b1iOcSuPMjHWOCVWNcnQuKPxNnka7A==
X-ME-Sender: <xms:np7KZDOIYqK3FF4nVyVGxunAVHLen-XtUPmuwN3DJMu89m93WE-WsA> <xme:np7KZN_rS7sdoyw68GK0lRfbXfVT_SVyI1n4C8VjlenMiK645_CSxvEk8YYN66YTL dpuw65LaQp6lQWPNg>
X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgedviedrkedtgddvkecutefuodetggdotefrodftvf curfhrohhfihhlvgemucfhrghsthforghilhdpqfgfvfdpuffrtefokffrpgfnqfghnecu uegrihhlohhuthemuceftddtnecunecujfgurhepofgfggfkjghffffhvffutgesthdtre dtreertdenucfhrhhomhepfdetlhgvgigrnhguvghrucevlhhouhhtvghrfdcuoegrlhgv gidoihgvthhfsegtohhrvghmvghmrdgtohhmqeenucggtffrrghtthgvrhhnpedvteejhf ehgfegleeuleefteeikefgvefhheekheevvdekueefkeeiieffhfdvgeenucevlhhushht vghrufhiiigvpedtnecurfgrrhgrmhepmhgrihhlfhhrohhmpegrlhgvgidoihgvthhfse gtohhrvghmvghmrdgtohhm
X-ME-Proxy: <xmx:np7KZCQgMsCbE-5xzgrpc28fziRuBkPZ4N7bn7i91gbt6r_BNAKhjA> <xmx:np7KZHtzS_x2Ti8oiCD9LNOIM31Whx89M8JUDrVc__0lXPORwh8P4g> <xmx:np7KZLdxiJF9wgw6filxp-vTszB4IeJRUPKPUpB1jmyDYMFQEZfdbg> <xmx:n57KZFqm-glfBG8L07KHICN05QOigWtYOm_VB-NLYtLF2uudMnQXBA>
Feedback-ID: ie3614602:Fastmail
Received: by mailuser.nyi.internal (Postfix, from userid 501) id B730A2A20085; Wed, 2 Aug 2023 14:21:18 -0400 (EDT)
X-Mailer: MessagingEngine.com Webmail Interface
User-Agent: Cyrus-JMAP/3.9.0-alpha0-624-g7714e4406d-fm-20230801.001-g7714e440
Mime-Version: 1.0
Message-Id: <f8a1e800-e4cc-4ed8-aaa6-d2eca1e20764@app.fastmail.com>
In-Reply-To: <ee50a5e6-8bee-09d4-15fa-cfce02a9e4bb@dfn.de>
References: <a401c4c2-3ddd-3d93-3fbc-b3fc02a1d26c@dfn.de> <CB09256A-196E-451F-B438-A1D0F392B9A1@deployingradius.com> <ee50a5e6-8bee-09d4-15fa-cfce02a9e4bb@dfn.de>
Date: Wed, 02 Aug 2023 19:20:58 +0100
From: Alexander Clouter <alex+ietf@coremem.com>
To: radext@ietf.org
Content-Type: text/plain
Archived-At: <https://mailarchive.ietf.org/arch/msg/radext/olFKdkB11UsaXBnPxu2zwTW43YU>
Subject: Re: [radext] Watchdog behaviour (was: Confirmation of discussions on RADIUS/(D)TLS at IETF117)
X-BeenThere: radext@ietf.org
X-Mailman-Version: 2.1.39
Precedence: list
List-Id: RADIUS EXTensions working group discussion list <radext.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/radext>, <mailto:radext-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/radext/>
List-Post: <mailto:radext@ietf.org>
List-Help: <mailto:radext-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/radext>, <mailto:radext-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 02 Aug 2023 18:21:41 -0000
On Wed, 2 Aug 2023, at 18:29, Jan-Frederik Rieckers wrote:
>
> Regarding the watchdog algorithm a question just popped up in my head
> and from the recording of the session I'm not exactly sure what the best
> course of action would be or what the opinion of people in the room is/was.
>
> Radsecproxy offers two different ways of doing status server. Either
> "on", which sends a packet each $timeinterval (I think it's 30 or 60
> seconds, would need to confirm) or "minimal" which only sends status
> server requests if replies to requests are outstanding.
>
> From my short skimming of RFC3539, only the latter is in compliance to
> the spec.
My skim makes me think neither approach is in compliance, but then this is a SHOULD not a MUST on the suggested implementation.
If your description of 'minimal' is true, I suspect its purpose is more a NAT keep-alive rather than a watchdog.
> Especially for debugging purposes and easy "grep" commands, it is quite
> helpful that you have a fairly regular status server log entry for each
> peer, because this way you don't have to analyze a lot of log lines, you
> just can have a nagios check to see if this specific well-structured
> line appeared in the logs during the last 2 minutes. If not, then
> something's wrong.
...just as easy to catch a non-zero count of access-{accept,reject}/accounting-response.
Of course you would *also* need to catch those Status-Server messages so a counter-argument would be "but now I have to use 'grep -e foo -e bar -e thingy ...' when I have to do Status-Server anyway...".
> In my opinion, the additional traffic of sending a status server request
> periodically instead of waiting until it is actually needed is
> negligible and since the ID 0 is reserved for it anyhow, it should not
> have further effect that an additional few bytes every few seconds.
Two angles I see.
Status-Server may be cheap on the wire, but I would be concerned about overlooking how cheap it may be to process. If the destination is a IdP, it would be useful if that check told you more whether the database it relies on is responsive rather than just if the listening socket is unclogged. So as an administrator of an IdP, for both monitoring and "making it meaningful", I personally like to make these sorts of requests an expensive operation (eg. poking a backend database). So one argument would be, maybe we want to keep these to a minimum.
Another angle is the impact this has on RADIUS implementation, I thin it would be a positive one (similar to "implement DTLS also"). Any state machine here needs to handle "idle" and "down" states so by tying Status-Server to only your idle state is not going to be too much of a problem. If you do not have a state machine for your communication with upstream proxies...well, you got other problems.
The aim of the watchdog is really to kick off failover sooner and preferably before you start sending actual traffic at it would would bubble up problems to your users...meaning the consequences are you may actually have to speak to them...eek! Best avoided!
> The relevant question here is: Do we add some additional text to allow
> deviating from the watchdog behavior described in RFC3539? Do we
> explicitly forbid it?
I would not forbid deviation, there are some special snowflake deployments out there. I think having SHOULD is strong enough to indicate "if you know what you are doing, go wild...".
> Or am I missing something and the habit of sending this periodically is
> actually more harmful than I can see?
If it is unnecessary the only thing it can do is result in harm. I am not convinced it would, but I am concerned that someone may have a costly operation backing onto Status-Server omstly as I think it is arguably prudent to do so.
Cheers
- [radext] Confirmation of discussions on RADIUS/(D… Jan-Frederik Rieckers
- Re: [radext] Confirmation of discussions on RADIU… Alan DeKok
- Re: [radext] Confirmation of discussions on RADIU… Bernard Aboba
- Re: [radext] Watchdog behaviour (was: Confirmatio… Jan-Frederik Rieckers
- Re: [radext] Watchdog behaviour (was: Confirmatio… Alexander Clouter
- Re: [radext] Watchdog behaviour (was: Confirmatio… Bernard Aboba
- Re: [radext] Watchdog behaviour (was: Confirmatio… Mark Grayson (mgrayson)
- Re: [radext] Watchdog behaviour (was: Confirmatio… Heikki Vatiainen
- Re: [radext] Watchdog behaviour (was: Confirmatio… Alexander Clouter
- Re: [radext] Watchdog behaviour (was: Confirmatio… Jan-Frederik Rieckers
- Re: [radext] Watchdog behaviour (was: Confirmatio… Heikki Vatiainen
- Re: [radext] Watchdog behaviour (was: Confirmatio… Margaret Cullen
- Re: [radext] Watchdog behaviour (was: Confirmatio… Alan DeKok
- Re: [radext] Watchdog behaviour (was: Confirmatio… Margaret Cullen
- Re: [radext] Confirmation of discussions on RADIU… Alexander Clouter
- Re: [radext] Confirmation of discussions on RADIU… Margaret Cullen
- Re: [radext] Confirmation of discussions on RADIU… Alexander Clouter
- Re: [radext] Confirmation of discussions on RADIU… Michael Richardson
- Re: [radext] Confirmation of discussions on RADIU… Heikki Vatiainen
- Re: [radext] Confirmation of discussions on RADIU… Peter Deacon
- Re: [radext] Confirmation of discussions on RADIU… Alan DeKok
- Re: [radext] Confirmation of discussions on RADIU… Peter Deacon
- Re: [radext] Confirmation of discussions on RADIU… Alan DeKok
- Re: [radext] Confirmation of discussions on RADIU… josh.howlett
- Re: [radext] Confirmation of discussions on RADIU… Jan-Frederik Rieckers
- Re: [radext] Confirmation of discussions on RADIU… Margaret Cullen
- Re: [radext] Confirmation of discussions on RADIU… Alan DeKok
- Re: [radext] Confirmation of discussions on RADIU… Michael Richardson
- Re: [radext] Confirmation of discussions on RADIU… Heikki Vatiainen
- Re: [radext] Confirmation of discussions on RADIU… Alexander Clouter