IETF Logo Mail Archive

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

Sam Hartman <hartmans@painless-security.com> Tue, 18 February 2014 15:56 UTC

Return-Path: <hartmans@painless-security.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 77F5B1A04CB for <radext@ietfa.amsl.com>; Tue, 18 Feb 2014 07:56:53 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.448
X-Spam-Level:
X-Spam-Status: No, score=-2.448 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RP_MATCHES_RCVD=-0.548] 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 SI1ZJlGkadOb for <radext@ietfa.amsl.com>; Tue, 18 Feb 2014 07:56:48 -0800 (PST)
Received: from mail.painless-security.com (mail.painless-security.com [23.30.188.241]) by ietfa.amsl.com (Postfix) with ESMTP id DFEEE1A01F0 for <radext@ietf.org>; Tue, 18 Feb 2014 07:56:47 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by mail.painless-security.com (Postfix) with ESMTP id 2BD6F20685; Tue, 18 Feb 2014 10:52:52 -0500 (EST)
Received: from mail.painless-security.com ([127.0.0.1]) by localhost (mail.suchdamage.org [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id cT4q1F2Z1yJy; Tue, 18 Feb 2014 10:52:51 -0500 (EST)
Received: from carter-zimmerman.suchdamage.org (unknown [10.1.10.106]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "laptop", Issuer "laptop" (not verified)) by mail.painless-security.com (Postfix) with ESMTPS; Tue, 18 Feb 2014 10:52:51 -0500 (EST)
Received: by carter-zimmerman.suchdamage.org (Postfix, from userid 8042) id 87BF283EAC; Tue, 18 Feb 2014 10:56:43 -0500 (EST)
From: Sam Hartman <hartmans@painless-security.com>
To: Alan DeKok <aland@deployingradius.com>
References: <tsl4n44rr3y.fsf@mit.edu> <CCE45314-4EFE-4C64-9794-85006392F834@gmail.com> <CAC8QAcePKh4KC=8fY69N4HWPfk=-XXCYxZRwf-uTq07jO3qYsQ@mail.gmail.com> <52FFED0D.2090104@deployingradius.com>
Date: Tue, 18 Feb 2014 10:56:43 -0500
In-Reply-To: <52FFED0D.2090104@deployingradius.com> (Alan DeKok's message of "Sat, 15 Feb 2014 17:41:17 -0500")
Message-ID: <tslha7w9zyc.fsf@mit.edu>
User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/23.4 (gnu/linux)
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Archived-At: http://mailarchive.ietf.org/arch/msg/radext/bXXzwkIUZlnsh06HWh5oUWAlywI
Cc: "radext@ietf.org" <radext@ietf.org>, sarikaya@ieee.org, Jouni <jouni.nospam@gmail.com>
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: Tue, 18 Feb 2014 15:56:53 -0000

>>>>> "Alan" == Alan DeKok <aland@deployingradius.com> writes:

    Alan> 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.

    Alan>   The Diameter considerations could say something like:

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

Yeah, that's the easy part.
The hard part is what to do about the  response-length attribute.
I wrote up some of the issues in a previous message.

v2.23.0 | Report a Bug | By Email