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

Alan DeKok <> Mon, 06 August 2018 12:59 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id 759BC130DDA; Mon, 6 Aug 2018 05:59:48 -0700 (PDT)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -1.901
X-Spam-Status: No, score=-1.901 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id QiwS219vY3WX; Mon, 6 Aug 2018 05:59:43 -0700 (PDT)
Received: from ( []) by (Postfix) with ESMTP id A4A96130DFD; Mon, 6 Aug 2018 05:59:43 -0700 (PDT)
Received: from [] ( []) by (Postfix) with ESMTPSA id 9E8C32C6; Mon, 6 Aug 2018 12:59:41 +0000 (UTC)
Mime-Version: 1.0 (Mac OS X Mail 9.3 \(3124\))
Content-Type: text/plain; charset=us-ascii
From: Alan DeKok <>
X-Priority: Medium
In-Reply-To: <>
Date: Mon, 6 Aug 2018 08:59:39 -0400
Cc: dime <>, iana <>,, Benjamin Kaduk <>
Content-Transfer-Encoding: quoted-printable
Message-Id: <>
References: <>
To: Denis Ovsienko <>
X-Mailer: Apple Mail (2.3124)
Archived-At: <>
Subject: Re: [radext] [Dime] error in IANA allocations for RFC 5447 (attributes 124 and 125)
X-Mailman-Version: 2.1.27
Precedence: list
List-Id: RADIUS EXTensions working group discussion list <>
List-Unsubscribe: <>, <>
List-Archive: <>
List-Post: <>
List-Help: <>
List-Subscribe: <>, <>
X-List-Received-Date: Mon, 06 Aug 2018 12:59:49 -0000

On Aug 6, 2018, at 8:01 AM, Denis Ovsienko <> wrote:
> 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 lists both attributes with wrong types:
> 125 	MIP6-Home-Link-Prefix 	ipv6prefix 	[RFC5447]

  That is definitely wrong.  The "ipv6prefix" format is different than the one used by MIP6-Home-Link-Prefix in RFC 5337.

> 124 	MIP6-Feature-Vector 	string 	[RFC5447]

  That issue is a bit different.  64-bit integers were defined in RFC 6929 ( long after RFC 5447 was published.

  So at the time RFC 5447 was published, "string" was the correct definition.

> 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 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?

 In the end, I think that the incorrect IANA allocations were a result of the updates done in RFC 8044.  The early drafts had a table which updated all of the IANA data types, e.g.:

  The MIP6 attributes are listed there as "ipv6prefix" and "string".  As the author of RFC 8044, I think that's my mistake.  Updating hundreds of attributes required reading many RFCs, and it's understandable that a few mistakes were made.

  Unless there are objections from DIME or RADEXT, I think it would be best for IANA to update the registry as follows:

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

  We may need approval from the AD (Ben).  Explicit consensus from the WG would also be helpful.

  Alan DeKok.