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

Jouni Korhonen <jouni.nospam@gmail.com> Wed, 19 February 2014 07:48 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 DDB6A1A056E for <radext@ietfa.amsl.com>; Tue, 18 Feb 2014 23:48:18 -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 eWUC4MZSd9QR for <radext@ietfa.amsl.com>; Tue, 18 Feb 2014 23:48:16 -0800 (PST)
Received: from mail-la0-x22e.google.com (mail-la0-x22e.google.com [IPv6:2a00:1450:4010:c03::22e]) by ietfa.amsl.com (Postfix) with ESMTP id 8FF4C1A056D for <radext@ietf.org>; Tue, 18 Feb 2014 23:48:16 -0800 (PST)
Received: by mail-la0-f46.google.com with SMTP id b8so25093lan.5 for <radext@ietf.org>; Tue, 18 Feb 2014 23:48:12 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=content-type:mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; bh=0RzWxOiU0azojL7SAKQ4lkFPsOdCwLZBT/l7lx1zaBU=; b=hF8j0V6+IrgLLOIlzltur1kHpURxE1dG7KcTZZ0o4mc0Xojc/suF838iyjWhFWpA/W Cu6stWZXWnii+hhxCXuKaM48quP8uKZreVvHerb24VR76sWG4LZnVgieJBxJBxRZyeDe zqQxVzcmoUywpZgbd90Tvkhakg+ZZ5q7lRH7Is5t68qXeP/EmTSwOkaF+sutHtIxfaP3 SrvzuR9OillLIG6HCKJT1VI+ChgE8xWguc5MWQ1wb//Cv0r5Mt7n2itmEtWu8Ck7uUJC Xbq49ZoFcS6NYUQWumC7gv6GLznNl0OCArk5ulqjsNC6U6rNziFISc0FIxkmtyhMcoQs SZoQ==
X-Received: by 10.152.30.68 with SMTP id q4mr981096lah.44.1392796092745; Tue, 18 Feb 2014 23:48:12 -0800 (PST)
Received: from [188.117.15.108] ([188.117.15.108]) by mx.google.com with ESMTPSA id gb8sm26559269lbc.13.2014.02.18.23.48.08 for <multiple recipients> (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Tue, 18 Feb 2014 23:48:09 -0800 (PST)
Content-Type: text/plain; charset="us-ascii"
Mime-Version: 1.0 (Mac OS X Mail 6.6 \(1510\))
From: Jouni Korhonen <jouni.nospam@gmail.com>
In-Reply-To: <tslvbwkqc2x.fsf@mit.edu>
Date: Wed, 19 Feb 2014 09:48:08 +0200
Content-Transfer-Encoding: quoted-printable
Message-Id: <55C79EA7-9120-4342-B450-283A4D5A60BB@gmail.com>
References: <tsl4n44rr3y.fsf@mit.edu> <CCE45314-4EFE-4C64-9794-85006392F834@gmail.com> <tslvbwkqc2x.fsf@mit.edu>
To: Sam Hartman <hartmans@painless-security.com>
X-Mailer: Apple Mail (2.1510)
Archived-At: http://mailarchive.ietf.org/arch/msg/radext/Sis5PUigd5CyYEEWOSPBeTUeX9w
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, 19 Feb 2014 07:48:19 -0000

RFC4005bis i.e. to be RFC7155 has obsoleted all the automatic 
RADIUS-Diameter translation. It really is up to a specific
deployment and a specific document to define one. No one is
going to ask you for one from the process point of view but
you are of course free to do one. Though,  I would argue that
you need to go greater lengths than a paragraph to explain
Diameter considerations for this specification.

- Jouni


On Feb 12, 2014, at 11:02 PM, Sam Hartman <hartmans@painless-security.com> wrote:

>>>>>> "Jouni" == Jouni  <jouni.nospam@gmail.com> writes:
> 
>    Jouni> One serious suggestion is just dropping the Diameter
>    Jouni> considerations unless you really insist doing one. We have
>    Jouni> not required one for some time already and that has not been
>    Jouni> an issue during the publication process.
> 
> 
> Great suggestion!
> It's there only because back when I was on the IESG they seemed to be
> required and I assumed they still were.