IETF Logo Mail Archive

Re: [radext] configuration auto-discovery [was: draft-cullen-radextra-status-realm-00]

Michael Richardson <mcr+ietf@sandelman.ca> Sun, 13 August 2023 23:16 UTC

Return-Path: <mcr+ietf@sandelman.ca>
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 5E199C14E513 for <radext@ietfa.amsl.com>; Sun, 13 Aug 2023 16:16:54 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.107
X-Spam-Level:
X-Spam-Status: No, score=-2.107 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_ZEN_BLOCKED_OPENDNS=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01, 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=sandelman.ca
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 eAIJ7zL284kH for <radext@ietfa.amsl.com>; Sun, 13 Aug 2023 16:16:49 -0700 (PDT)
Received: from tuna.sandelman.ca (tuna.sandelman.ca [IPv6:2607:f0b0:f:3:216:3eff:fe7c:d1f3]) (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 6D1D4C14E515 for <radext@ietf.org>; Sun, 13 Aug 2023 16:16:49 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by tuna.sandelman.ca (Postfix) with ESMTP id 72CFE3898C; Sun, 13 Aug 2023 19:16:47 -0400 (EDT)
Received: from tuna.sandelman.ca ([127.0.0.1]) by localhost (localhost [127.0.0.1]) (amavisd-new, port 10024) with LMTP id YtWmN7cEmRRo; Sun, 13 Aug 2023 19:16:46 -0400 (EDT)
Received: from sandelman.ca (obiwan.sandelman.ca [209.87.249.21]) by tuna.sandelman.ca (Postfix) with ESMTP id B96153898B; Sun, 13 Aug 2023 19:16:46 -0400 (EDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=sandelman.ca; s=mail; t=1691968606; bh=PcPWOLzUN1brmnHer4TBkConf3RNJLKglwU1ZmA9Nr4=; h=From:To:Subject:In-Reply-To:References:Date:From; b=skdUs8tSYdNGd7zGUDmY6ZDh/MChVoOHyXpC/ecKApB5YqcqB8Oe3aK+7pm2E092u dsFDxM9NVz7NnZ3c03yyaQNIB07td56d/q97VO9cMJbKkpFtgNWipmeDuojK3OlgZN V9CfKoJDPYXpNJpmPIG/gMHAdolU+Id/TAeUkZzqvg7LzDhOQ0ud4Z9w8owIalxvv/ FNAOqDBziNvk6YOCmNqdFQ/W1qzCXrNA0OVSWNazQ5akM5zYEJsDf1qUvsCwLQqdim l1IQIpOdc8+3rkgHtWE4VA5VXizKOyAGDLnO3vmmKJUV7ZVAcC1ZOxKnoV7uScDWz0 dywVS6tgCZLeQ==
Received: from localhost (localhost [IPv6:::1]) by sandelman.ca (Postfix) with ESMTP id ADBDC2C7; Sun, 13 Aug 2023 19:16:46 -0400 (EDT)
From: Michael Richardson <mcr+ietf@sandelman.ca>
To: Alan DeKok <aland@deployingradius.com>, radext@ietf.org
In-Reply-To: <3CAEA649-7996-4564-B6C9-7B28DD32FDDA@deployingradius.com>
References: <0FCC9942-32CE-4B98-8F71-175F410882E7@deployingradius.com> <5B16D759-758E-4701-8C7E-4A563AC74274@gmail.com> <3CAEA649-7996-4564-B6C9-7B28DD32FDDA@deployingradius.com>
X-Mailer: MH-E 8.6+git; nmh 1.7+dev; GNU Emacs 27.1
X-Face: $\n1pF)h^`}$H>Hk{L"x@)JS7<%Az}5RyS@k9X%29-lHB$Ti.V>2bi.~ehC0; <'$9xN5Ub# z!G,p`nR&p7Fz@^UXIn156S8.~^@MJ*mMsD7=QFeq%AL4m<nPbLgmtKK-5dC@#:k
MIME-Version: 1.0
Content-Type: multipart/signed; boundary="=-=-="; micalg="pgp-sha512"; protocol="application/pgp-signature"
Date: Sun, 13 Aug 2023 19:16:46 -0400
Message-ID: <22227.1691968606@localhost>
Archived-At: <https://mailarchive.ietf.org/arch/msg/radext/GrciG5hmZB8xoC0E5QZLN-s09fk>
Subject: Re: [radext] configuration auto-discovery [was: draft-cullen-radextra-status-realm-00]
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: Sun, 13 Aug 2023 23:16:54 -0000

Alan DeKok <aland@deployingradius.com> wrote:
    >   There are a few use-cases which could be solved.  A routing protocol
    > may be the solution, or perhaps something simpler.

    >   One is that fail-over is just not defined at all in RFC 2865.  RFC
    > 3539 defines a way to tell if a particular connection is alive.  But no
    > specification describes how to fail over between connections, or
    > load-balancing mechanisms, or how to address multi-hop issues.

    >   This lack means that any fail-over mechanism is largely
    > implementation-defined.  Which means there are often connection /
    > destination flapping, similar to route flaps.

    >   There is no way for a proxy to say "I'm alive, but I can't route this
    > particular packet.  Please redirect it somewhere else".  Better
    > connection signalling would solve that issue directly.  A routing
    > protocol would solve it indirectly.

It sounds more like an MPTCP situation than routing, exactly.
(not that I'm suggesting RADIUS/TCP/TLS use MPTCP itself)

--
Michael Richardson <mcr+IETF@sandelman.ca>   . o O ( IPv6 IøT consulting )
           Sandelman Software Works Inc, Ottawa and Worldwide

v2.35.0 | Report a Bug | By Email | System Status