IETF Logo Mail Archive

Re: [radext] Proposed charter text based on IETF-115 BoF

Alan DeKok <aland@deployingradius.com> Tue, 22 November 2022 19:47 UTC

Return-Path: <aland@deployingradius.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 E7D82C1522B1 for <radext@ietfa.amsl.com>; Tue, 22 Nov 2022 11:47:09 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.899
X-Spam-Level:
X-Spam-Status: No, score=-1.899 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, 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 13Yri-oRmU3i for <radext@ietfa.amsl.com>; Tue, 22 Nov 2022 11:47:04 -0800 (PST)
Received: from mail.networkradius.com (mail.networkradius.com [62.210.147.122]) (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 4F90AC1522D1 for <radext@ietf.org>; Tue, 22 Nov 2022 11:47:03 -0800 (PST)
Received: from smtpclient.apple (135-23-95-173.cpe.pppoe.ca [135.23.95.173]) by mail.networkradius.com (Postfix) with ESMTPSA id 8384655D; Tue, 22 Nov 2022 19:47:00 +0000 (UTC)
Authentication-Results: NetworkRADIUS; dmarc=none (p=none dis=none) header.from=deployingradius.com
Content-Type: text/plain; charset="us-ascii"
Mime-Version: 1.0 (Mac OS X Mail 16.0 \(3696.120.41.1.1\))
From: Alan DeKok <aland@deployingradius.com>
In-Reply-To: <8250.1669140392@localhost>
Date: Tue, 22 Nov 2022 14:46:58 -0500
Cc: radext@ietf.org
Content-Transfer-Encoding: quoted-printable
Message-Id: <F377FB99-33AB-4602-AE8D-2C6B80B0B109@deployingradius.com>
References: <CAGL5yWYTzvN1SgL8ordMvenhDGMs-EZw32+U32_4jeR9mqGciQ@mail.gmail.com> <81A072E3-88E2-432F-8672-A068DF41FAB4@deployingradius.com> <8250.1669140392@localhost>
To: Michael Richardson <mcr+ietf@sandelman.ca>
X-Mailer: Apple Mail (2.3696.120.41.1.1)
Archived-At: <https://mailarchive.ietf.org/arch/msg/radext/Qy2gPQEIZRrWRPq8tzRzOeRcwa4>
Subject: Re: [radext] Proposed charter text based on IETF-115 BoF
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: Tue, 22 Nov 2022 19:47:10 -0000

On Nov 22, 2022, at 1:06 PM, Michael Richardson <mcr+ietf@sandelman.ca> wrote:
> Alan DeKok <aland@deployingradius.com> wrote:
>> 1) Write a document giving guidance on using TLS-PSK with TLS and DTLS.
> 
> Wow, I'd sure rather encourage use DANE keys in DNS or copy-and-pasted raw
> keys rather than PSK.  I can see that there is an upgrade path that might be
> important...

  That might be possible.  But experience shows that it's difficult to even get shred secrets correct.  Adding yet more dependencies to RADIUS seems difficult.

> I think that the major hurdle for using RPK is possibly that we haven't made
> operators aware of something clearly and easily copy and pasted.

  OpenSSL doesn't support RFC 7250.  That makes it difficult.

>> 2) define (or investigate defining) a "hop by hop" signalling packet.
> 
> Do you mean a hop-by-hop RADIUS packet, or a hop-by-hop DTLS packet?

  I mean that there are a few RFCs which "overload" Status-Server to do per-hop signalling.  If there's a wide-spread use for per-hop signalling / negotiation, then we might as well define an explicit per-hop signalling packet.

  RFC 5997 defined Status-Server as either an application-layer "ping", or as an RFC 3539 application-layer watchdog timer.  Other uses-cases are arguably mis-uses.

  Alan DeKok.

v2.23.0 | Report a Bug | By Email