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

Denis Ovsienko <denis@ovsienko.info> Mon, 13 August 2018 21:28 UTC

Return-Path: <denis@ovsienko.info>
X-Original-To: dime@ietfa.amsl.com
Delivered-To: dime@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5CF1C1310DC for <dime@ietfa.amsl.com>; Mon, 13 Aug 2018 14:28:50 -0700 (PDT)
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, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001, URIBL_BLOCKED=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 ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id etz_sFdWuXlQ for <dime@ietfa.amsl.com>; Mon, 13 Aug 2018 14:28:49 -0700 (PDT)
Received: from sender-of-o51.zoho.com (sender-of-o51.zoho.com [135.84.80.216]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 02D9813102C for <dime@ietf.org>; Mon, 13 Aug 2018 14:28:48 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; t=1534195728; s=zohomail; d=ovsienko.info; i=denis@ovsienko.info; h=Date:From:To:Message-ID:In-Reply-To:References:Subject:MIME-Version:Content-Type:Content-Transfer-Encoding; l=736; bh=Gd49HTIxLiIROPYu9uIquS60SnEVKK/e4Zagvu5GoIw=; b=bVahSy5H5w2G37Y8Bm93uqvjXPKgaeUYMrhXAySONmQwaOHhavlitEKHO3RCNRti a6tiAZvEVj/bSvzLRFSNtRmCmjz80dnSguuP1+ntGDGnBijr0A408W3mbFgkXpinhN/ +RKZ+WsskEZeqG6x2Gzo/bmWRK1NZLX/3csKfPj8=
Received: from mail.zoho.com by mx.zohomail.com with SMTP id 1534195726477421.3541318617969; Mon, 13 Aug 2018 14:28:46 -0700 (PDT)
Date: Mon, 13 Aug 2018 22:28:46 +0100
From: Denis Ovsienko <denis@ovsienko.info>
To: "Alan DeKok" <aland@deployingradius.com>, "dime" <dime@ietf.org>
Message-ID: <1653530f88b.ddb4852f136444.182877631447793885@ovsienko.info>
In-Reply-To: <A54682E8-B80C-4992-877C-218B492882E3@deployingradius.com>
References: <1650f1cabeb.100024af647180.2934901912766753218@ovsienko.info> <A54682E8-B80C-4992-877C-218B492882E3@deployingradius.com>
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/Nhk9vJRJjjyNvDBuyKP_6ngDixw>
Subject: Re: [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, 13 Aug 2018 21:28:50 -0000

 ---- On Mon, 06 Aug 2018 13:59:39 +0100 Alan DeKok <aland@deployingradius.com> wrote ---- 
[...]
 >  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.: 
 >  
 > https://tools.ietf.org/html/draft-ietf-radext-datatypes-05#section-4.2 
 >  
 >   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. 
[...]

Everybody makes mistakes. Not everybody has the capability to admit and put it right. Well done.

-- 
    Denis Ovsienko