IETF Logo Mail Archive

Re: [radext] draft-cullen-radextra-status-realm-00

Alan DeKok <aland@deployingradius.com> Wed, 26 April 2023 16:26 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 9AB00C14CE4F for <radext@ietfa.amsl.com>; Wed, 26 Apr 2023 09:26:43 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.899
X-Spam-Level:
X-Spam-Status: No, score=-6.899 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_HI=-5, 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 bITbppBSy96g for <radext@ietfa.amsl.com>; Wed, 26 Apr 2023 09:26:39 -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 2A592C14CF12 for <radext@ietf.org>; Wed, 26 Apr 2023 09:26:38 -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 4335A26F; Wed, 26 Apr 2023 16:26:35 +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: <1393972.1682517148@dyas>
Date: Wed, 26 Apr 2023 12:26:33 -0400
Cc: radext@ietf.org
Content-Transfer-Encoding: quoted-printable
Message-Id: <8C407B61-9ADF-480F-A1ED-5CA7EED9C125@deployingradius.com>
References: <CANsiXEK56aVwtjGqrLYsq-syC=zrHVqNzgKV7_gkkZXAkQhQ=w@mail.gmail.com> <DA1886A1-7295-445F-BA46-A342CBECC9DC@deployingradius.com> <1393972.1682517148@dyas>
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/j34cRkmCLmJzrzKTkuUcUpQR6bQ>
Subject: Re: [radext] 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: Wed, 26 Apr 2023 16:26:43 -0000

On Apr 26, 2023, at 9:52 AM, Michael Richardson <mcr+ietf@sandelman.ca> wrote:
> I think you explained 4K to me before, but with radius/1.1, is it worth
> setting a higher maximum size?  Or providing a way for each hop to express
> it's maximum?

  RFC 7930 defines these mechanisms.  It's probably worth noting that RADIUS/1.1 doesn't change the 4K limit.

  Alan DeKok.

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