IETF Logo Mail Archive

Re: [radext] RADIUS/(D)TLS port usage (was: Review of draft-ietf-radext-radiusdtls)

Alan DeKok <aland@deployingradius.com> Wed, 10 April 2024 20:09 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 A3692C14F5F4 for <radext@ietfa.amsl.com>; Wed, 10 Apr 2024 13:09:45 -0700 (PDT)
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 dX9L_tqZFmXP for <radext@ietfa.amsl.com>; Wed, 10 Apr 2024 13:09:41 -0700 (PDT)
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 317FFC14EB19 for <radext@ietf.org>; Wed, 10 Apr 2024 13:09:40 -0700 (PDT)
Received: from smtpclient.apple (135-23-95-173.cpe.pppoe.ca [135.23.95.173]) by mail.networkradius.com (Postfix) with ESMTPSA id 64EED579; Wed, 10 Apr 2024 20:09:37 +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: <9611.1712778801@obiwan.sandelman.ca>
Date: Wed, 10 Apr 2024 16:09:35 -0400
Cc: Jan-Frederik Rieckers <rieckers@dfn.de>, radext@ietf.org
Content-Transfer-Encoding: quoted-printable
Message-Id: <489915B4-4033-4BA0-9548-20280B2F19E4@deployingradius.com>
References: <CA9BEA9C-39EF-4764-A0FE-D122413B37F7@deployingradius.com> <18ef8267-474e-49ae-9204-0c6c79d5e50c@dfn.de> <2e70196c-0def-401f-83ed-0eb924cc60eb@dfn.de> <9611.1712778801@obiwan.sandelman.ca>
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/GlUYgYtQnW9iZE0YDqtEe38fZ9c>
Subject: Re: [radext] RADIUS/(D)TLS port usage (was: Review of draft-ietf-radext-radiusdtls)
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, 10 Apr 2024 20:09:45 -0000

On Apr 10, 2024, at 3:53 PM, Michael Richardson <mcr+ietf@sandelman.ca> wrote:
> okay, I also agree.
> So what's the new ports?  Did we already have them?
> Do we have to ask for new ones (That's not a big deal, since we aren't asking
> for <1024)

  We already have 2083 assigned for UDP and TCP.  The old TLS documents mandate that they are used for RADIUS/(D)TLS, and that they're not used for old-style RADIUS.

  Alan DeKok.

v2.23.0 | Report a Bug | By Email