IETF Logo Mail Archive

Re: [radext] Client ID exhaustion

Ignacio Goyret <ignacio.goyret@nokia.com> Thu, 27 April 2017 18:51 UTC

Return-Path: <ignacio.goyret@nokia.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 DD1FC12944A for <radext@ietfa.amsl.com>; Thu, 27 Apr 2017 11:51:54 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -9.701
X-Spam-Level:
X-Spam-Status: No, score=-9.701 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_HI=-5, RCVD_IN_MSPIKE_H2=-2.8, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 80qhly6Rocjw for <radext@ietfa.amsl.com>; Thu, 27 Apr 2017 11:51:53 -0700 (PDT)
Received: from smtp-us.alcatel-lucent.com (us-hpswa-esg-02.alcatel-lucent.com [135.245.18.30]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id C6570129480 for <radext@ietf.org>; Thu, 27 Apr 2017 11:48:47 -0700 (PDT)
Received: from us70uumx4.dmz.alcatel-lucent.com (unknown [135.245.18.16]) by Websense Email Security Gateway with ESMTPS id 8BA025A1E7186; Thu, 27 Apr 2017 18:48:44 +0000 (GMT)
Received: from us70uusmtp4.zam.alcatel-lucent.com (us70uusmtp4.zam.alcatel-lucent.com [135.5.2.66]) by us70uumx4.dmz.alcatel-lucent.com (GMO) with ESMTP id v3RImkHY022934 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Thu, 27 Apr 2017 18:48:46 GMT
Received: from cliff.eng.ascend.com (cliff.eng.ascend.com [192.207.23.55]) by us70uusmtp4.zam.alcatel-lucent.com (GMO) with ESMTP id v3RImih3006571 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=FAIL); Thu, 27 Apr 2017 18:48:45 GMT
Received: from igoyret-c1.nokia.com (igoyret-pc [135.227.139.12]) by cliff.eng.ascend.com (8.13.1/8.13.1) with ESMTP id v3RIowo6026896 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Thu, 27 Apr 2017 11:50:59 -0700
Message-Id: <201704271850.v3RIowo6026896@cliff.eng.ascend.com>
X-Mailer: QUALCOMM Windows Eudora Version 7.1.0.9
Date: Thu, 27 Apr 2017 11:46:36 -0700
To: Alan DeKok <aland@deployingradius.com>
From: Ignacio Goyret <ignacio.goyret@nokia.com>
Cc: Enke Chen <enkechen@cisco.com>, radext@ietf.org
In-Reply-To: <B2D57E9F-C8B7-4E1C-9234-C1B41A08ABA7@deployingradius.com>
References: <f521cd74-028d-33e7-4b94-0a9d65bd7d37@restena.lu> <e4c8aee2-c97f-e89e-8b48-6c943651238f@cisco.com> <B2D57E9F-C8B7-4E1C-9234-C1B41A08ABA7@deployingradius.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Archived-At: <https://mailarchive.ietf.org/arch/msg/radext/UGSVd0A-qHsmEIwBhZMwkc3ksRs>
Subject: Re: [radext] Client ID exhaustion
X-BeenThere: radext@ietf.org
X-Mailman-Version: 2.1.22
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: Thu, 27 Apr 2017 18:51:55 -0000

At 08:09 4/27/2017, Alan DeKok wrote:

>  I've seen multiple situations where a high load RADIUS proxy continually has 32 or more source ports in use.  At that point, you have to ask if it isn't more efficient to just update RADIUS.

A better alternative is to use a more appropriate tool like Diameter
which solves all these issues quite well.

>  i.e. Asking implementations to open 1-4 source ports is reasonable.  Asking them to implement 2000 source ports for a high load situation is possible, but is less reasonable.

Dealing with thousands of ports requires extra care but it is not
an impossible task.

-Ignacio

v2.23.0 | Report a Bug | By Email