IETF Logo Mail Archive

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

Sam Hartman <hartmans@painless-security.com> Wed, 12 February 2014 20:52 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 764E11A06EA for <radext@ietfa.amsl.com>; Wed, 12 Feb 2014 12:52:24 -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 pcGQ-r1Z6e11 for <radext@ietfa.amsl.com>; Wed, 12 Feb 2014 12:52:21 -0800 (PST)
Received: from mail.painless-security.com (mail.painless-security.com [23.30.188.241]) by ietfa.amsl.com (Postfix) with ESMTP id D5E1E1A0665 for <radext@ietf.org>; Wed, 12 Feb 2014 12:52:20 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by mail.painless-security.com (Postfix) with ESMTP id 5921220675 for <radext@ietf.org>; Wed, 12 Feb 2014 15:48:40 -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 f3Q9cih0ZNWR for <radext@ietf.org>; Wed, 12 Feb 2014 15:48:39 -0500 (EST)
Received: from carter-zimmerman.suchdamage.org (c-50-177-27-27.hsd1.ma.comcast.net [50.177.27.27]) (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 for <radext@ietf.org>; Wed, 12 Feb 2014 15:48:39 -0500 (EST)
Received: by carter-zimmerman.suchdamage.org (Postfix, from userid 8042) id 6479083E0B; Wed, 12 Feb 2014 15:52:17 -0500 (EST)
From: Sam Hartman <hartmans@painless-security.com>
To: radext@ietf.org
Date: Wed, 12 Feb 2014 15:52:17 -0500
Message-ID: <tsl4n44rr3y.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"
Subject: [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: Wed, 12 Feb 2014 20:52:24 -0000

Hi folks.  I could use some help with the diameter considerations
section for draft-hartman-radext-bigger-packets.

First, what value should  a proxy forwarding from a diameter client to a
radius server include for the maximum-response-length attribute?

When forwarding from radius towards a diameter server, what should
happen with regard to the maximum-response-length attribute:

* Strip it as diameter doesn't expect it

* Keep it if present.  Perhaps diameter will trim down its response

* Insert it  if the transport in the radius direction is UDP--after all,
  might as well let diameter know what's going on.

Another thing to consider here is interactions with
radius-diameter-radius situations.

--Sam

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