IETF Logo Mail Archive

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

Jouni <jouni.nospam@gmail.com> Wed, 12 February 2014 20:58 UTC

Return-Path: <jouni.nospam@gmail.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 78A631A0694 for <radext@ietfa.amsl.com>; Wed, 12 Feb 2014 12:58:51 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2
X-Spam-Level:
X-Spam-Status: No, score=-2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, SPF_PASS=-0.001] 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 lIlfVfiCvCrq for <radext@ietfa.amsl.com>; Wed, 12 Feb 2014 12:58:46 -0800 (PST)
Received: from mail-lb0-x22e.google.com (mail-lb0-x22e.google.com [IPv6:2a00:1450:4010:c04::22e]) by ietfa.amsl.com (Postfix) with ESMTP id 6A4CF1A06BC for <radext@ietf.org>; Wed, 12 Feb 2014 12:58:46 -0800 (PST)
Received: by mail-lb0-f174.google.com with SMTP id l4so7571391lbv.33 for <radext@ietf.org>; Wed, 12 Feb 2014 12:58:44 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=subject:mime-version:content-type:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; bh=jwc6rY8ta2hb+v471KkB6eoTCTbPxz8AFRATv3kvtD0=; b=HDkFVwmDmw3hwU36UFm1YOkbUCcjuQwzKJM1eu1v1JY8/5vk+TnsOLKZs/sGMhn6IU fTdoElskmbthbRmhyJ/aEXvFcHa/DbKCe7+0fdyj2du+/RMfnVjwGbgmAPYrelx9bSw1 Qw2vmnEtRmUmPcyLzJ9tGB+hJ4GPzGgETyhtjI7BVbR/JTqUvYygwWP6y5XcBhsP+QWd 9umbyWkxLH6pZaUFWMVnFgQ1XEhhCvg6WpxiM608D7nnpC+evkjck5QTE8ITRZLrw41L h25KCT5QC1CIBFlDt3qQJez07jKpXDKJpNeZFlRCBfYdAMHivRgYvsr506yHC2Y+qTjw QOeg==
X-Received: by 10.153.9.97 with SMTP id dr1mr3433418lad.45.1392238724823; Wed, 12 Feb 2014 12:58:44 -0800 (PST)
Received: from [188.117.15.107] ([188.117.15.107]) by mx.google.com with ESMTPSA id w2sm35091775lad.4.2014.02.12.12.58.41 for <multiple recipients> (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Wed, 12 Feb 2014 12:58:41 -0800 (PST)
Mime-Version: 1.0 (Apple Message framework v1283)
Content-Type: text/plain; charset="us-ascii"
From: Jouni <jouni.nospam@gmail.com>
In-Reply-To: <tsl4n44rr3y.fsf@mit.edu>
Date: Wed, 12 Feb 2014 22:58:40 +0200
Content-Transfer-Encoding: 7bit
Message-Id: <CCE45314-4EFE-4C64-9794-85006392F834@gmail.com>
References: <tsl4n44rr3y.fsf@mit.edu>
To: Sam Hartman <hartmans@painless-security.com>
X-Mailer: Apple Mail (2.1283)
Cc: 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: Wed, 12 Feb 2014 20:58:51 -0000

One serious suggestion is just dropping the Diameter considerations
unless you really insist doing one. We have not required one for some
time already and that has not been an issue during the publication
process.

- Jouni


On Feb 12, 2014, at 10:52 PM, Sam Hartman wrote:

> 
> 
> 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
> 
> _______________________________________________
> radext mailing list
> radext@ietf.org
> https://www.ietf.org/mailman/listinfo/radext

v2.23.0 | Report a Bug | By Email