IETF Logo Mail Archive

Re: [radext] Help with diameter considerations for draft-hartman-radext-bigger-packets

Alan DeKok <aland@deployingradius.com> Sat, 15 February 2014 22:41 UTC

Return-Path: <aland@deployingradius.com>
X-Original-To: radext@ietfa.amsl.com
Delivered-To: radext@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 0EF0C1A0163 for <radext@ietfa.amsl.com>; Sat, 15 Feb 2014 14:41:48 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level:
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9] autolearn=ham
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 5OCGXeKa4NnC for <radext@ietfa.amsl.com>; Sat, 15 Feb 2014 14:41:46 -0800 (PST)
Received: from power.freeradius.org (power.freeradius.org [88.190.25.44]) by ietfa.amsl.com (Postfix) with ESMTP id 8FCED1A0133 for <radext@ietf.org>; Sat, 15 Feb 2014 14:41:46 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by power.freeradius.org (Postfix) with ESMTP id 5E87B224016F; Sat, 15 Feb 2014 23:41:14 +0100 (CET)
X-Virus-Scanned: Debian amavisd-new at power.freeradius.org
Received: from power.freeradius.org ([127.0.0.1]) by localhost (power.freeradius.org [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id dsvt3uRl8KDW; Sat, 15 Feb 2014 23:41:14 +0100 (CET)
Received: from Thor.local (unknown [70.50.217.206]) by power.freeradius.org (Postfix) with ESMTPSA id 91F9922400A9; Sat, 15 Feb 2014 23:41:13 +0100 (CET)
Message-ID: <52FFED0D.2090104@deployingradius.com>
Date: Sat, 15 Feb 2014 17:41:17 -0500
From: Alan DeKok <aland@deployingradius.com>
User-Agent: Thunderbird 2.0.0.24 (Macintosh/20100228)
MIME-Version: 1.0
To: sarikaya@ieee.org
References: <tsl4n44rr3y.fsf@mit.edu> <CCE45314-4EFE-4C64-9794-85006392F834@gmail.com> <CAC8QAcePKh4KC=8fY69N4HWPfk=-XXCYxZRwf-uTq07jO3qYsQ@mail.gmail.com>
In-Reply-To: <CAC8QAcePKh4KC=8fY69N4HWPfk=-XXCYxZRwf-uTq07jO3qYsQ@mail.gmail.com>
Content-Type: text/plain; charset="ISO-8859-1"
Content-Transfer-Encoding: 7bit
Archived-At: http://mailarchive.ietf.org/arch/msg/radext/HliZLYxdmjDHp-jTrgEX0QOS4jA
Cc: Sam Hartman <hartmans@painless-security.com>, Jouni <jouni.nospam@gmail.com>, "radext@ietf.org" <radext@ietf.org>
Subject: Re: [radext] Help with diameter considerations for draft-hartman-radext-bigger-packets
X-BeenThere: radext@ietf.org
X-Mailman-Version: 2.1.15
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: <http://www.ietf.org/mail-archive/web/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: Sat, 15 Feb 2014 22:41:48 -0000

Behcet Sarikaya wrote:
> RADIUS - Diameter interworking is important for fmc (fixed mobile
> convergence), as you know the fixed network uses RADIUS and 3GPP uses
> Diameter. So for example when authenticating UE when connected via Wi-Fi
> to a fixed broadband network, this interworking is needed.

  The Diameter considerations could say something like:

Diameter already supports packets of 64K octets.  So any "large" RADIUS
packet can be transported in Diameter as-is.  Otherwise, any gateway
which does RADIUS to Diameter, or Diameter to RADIUS transport, MUST
follow this specification for any RADIUS interaction.

  Alan DeKok.

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