[Dime] error in IANA allocations for RFC 5447 (attributes 124 and 125)

Denis Ovsienko <denis@ovsienko.info> Mon, 06 August 2018 12:01 UTC

Return-Path: <denis@ovsienko.info>
X-Original-To: dime@ietfa.amsl.com
Delivered-To: dime@ietfa.amsl.com
Received: from localhost (localhost []) by ietfa.amsl.com (Postfix) with ESMTP id F3D35130DCC for <dime@ietfa.amsl.com>; Mon, 6 Aug 2018 05:01:09 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.001
X-Spam-Status: No, score=-2.001 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=ovsienko.info
Received: from mail.ietf.org ([]) by localhost (ietfa.amsl.com []) (amavisd-new, port 10024) with ESMTP id mFnk_vlf77x9 for <dime@ietfa.amsl.com>; Mon, 6 Aug 2018 05:01:08 -0700 (PDT)
Received: from sender-of-o51.zoho.com (sender-of-o51.zoho.com []) (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 41070130934 for <dime@ietf.org>; Mon, 6 Aug 2018 05:01:08 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; t=1533556862; s=zohomail; d=ovsienko.info; i=denis@ovsienko.info; h=Date:From:To:Message-ID:In-Reply-To:Subject:MIME-Version:Content-Type:Content-Transfer-Encoding; l=1054; bh=aO54SzLWsVdN95AFwmb9LaOoAlmZOxos3bVD9VBjozs=; b=SD0oQjr3q2GL1AEX2B+u0GezPaL+13ZgRZ3rUZMyWHFvjoVhYk7c42hEBX62GCzn 6HZDVSITf9N/1JieMc/kFZX2f/yHwoU2zU3FPXWmjcEuWLA8rS9GmSY+R6FFyv8xTYc OHImn/AyNjpbPz2DW1qm/jw8hI0+y6D1tmm5rILI=
Received: from mail.zoho.com by mx.zohomail.com with SMTP id 15335568619331022.7068283587669; Mon, 6 Aug 2018 05:01:01 -0700 (PDT)
Date: Mon, 06 Aug 2018 13:01:01 +0100
From: Denis Ovsienko <denis@ovsienko.info>
To: "dime" <dime@ietf.org>, "iana" <iana@iana.org>
Message-ID: <1650f1cabeb.100024af647180.2934901912766753218@ovsienko.info>
MIME-Version: 1.0
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: 7bit
X-Priority: Medium
User-Agent: Zoho Mail
X-Mailer: Zoho Mail
Archived-At: <https://mailarchive.ietf.org/arch/msg/dime/2WeYLLIWnJEYZ8reqWchp_lzBMw>
Subject: [Dime] error in IANA allocations for RFC 5447 (attributes 124 and 125)
X-BeenThere: dime@ietf.org
X-Mailman-Version: 2.1.27
Precedence: list
List-Id: Diameter Maintanence and Extentions Working Group <dime.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dime>, <mailto:dime-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/dime/>
List-Post: <mailto:dime@ietf.org>
List-Help: <mailto:dime-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dime>, <mailto:dime-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 06 Aug 2018 12:01:10 -0000


Recently I was reviewing some code that adds support for two RFC 5447 RADIUS AVPs below:

   The MIP6-Home-Link-Prefix AVP (AVP Code 125) is of type OctetString
   The MIP6-Feature-Vector AVP (AVP Code 124) is of type Unsigned64 and

It turned out, the current RADIUS Types registry at https://www.iana.org/assignments/radius-types/radius-types.xhtml lists both attributes with wrong types:

125 	MIP6-Home-Link-Prefix 	ipv6prefix 	[RFC5447]
124 	MIP6-Feature-Vector 	string 	[RFC5447]

Those incorrect types had propagated from the IANA registry into FreeRADIUS and Wireshark (both have been fixed now for MIP6-Home-Link-Prefix, see the discussion and the follow-ups at https://github.com/the-tcpdump-group/tcpdump/pull/636 if interested).

Having studied this discrepancy thoroughly, I had concluded the AVP definitions are correct in RFC 5447, so I did not file an erratum. The problem seems to be with those IANA allocations only. Could somebody review this issue and put the IANA allocations right?

Thank you.

    Denis Ovsienko