Re: [radext] Questions about draft-ietf-radext-bigger-packets-03

Alan DeKok <aland@deployingradius.com> Thu, 29 October 2015 12:29 UTC

Return-Path: <aland@deployingradius.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 6B6A61B2E67; Thu, 29 Oct 2015 05:29:00 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level:
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9] 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 dGmMIde1EwMi; Thu, 29 Oct 2015 05:28:58 -0700 (PDT)
Received: from power.freeradius.org (power.freeradius.org [195.154.231.44]) by ietfa.amsl.com (Postfix) with ESMTP id EC3911B2E69; Thu, 29 Oct 2015 05:28:57 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by power.freeradius.org (Postfix) with ESMTP id CF3A62240B13; Thu, 29 Oct 2015 13:28:26 +0100 (CET)
X-Virus-Scanned: Debian amavisd-new at power.freeradius.org
Received: from power.freeradius.org ([127.0.0.1]) by localhost (power.freeradius.org [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id TCeSkBC7eoWX; Thu, 29 Oct 2015 13:28:26 +0100 (CET)
Received: from [192.168.120.41] (24-246-5-242.cable.teksavvy.com [24.246.5.242]) by power.freeradius.org (Postfix) with ESMTPSA id CD15022407AB; Thu, 29 Oct 2015 13:28:25 +0100 (CET)
Content-Type: text/plain; charset="windows-1252"
Mime-Version: 1.0 (Mac OS X Mail 9.0 \(3094\))
From: Alan DeKok <aland@deployingradius.com>
In-Reply-To: <563204D9.1010401@restena.lu>
Date: Thu, 29 Oct 2015 08:28:24 -0400
Content-Transfer-Encoding: quoted-printable
Message-Id: <330BC5C5-D84D-4EEC-8656-47FEF6EE37D1@deployingradius.com>
References: <55D57021.8060308@restena.lu> <183E3AC7-A5CB-43D4-ADCA-E0B7DD04B43C@deployingradius.com> <563204D9.1010401@restena.lu>
To: Winter Stefan <stefan.winter@restena.lu>
X-Mailer: Apple Mail (2.3094)
Archived-At: <http://mailarchive.ietf.org/arch/msg/radext/Q_N0ocTbsuOquk-SFelzWYFqPjo>
Cc: "radext@ietf.org" <radext@ietf.org>, draft-ietf-radext-bigger-packets.authors@ietf.org
Subject: Re: [radext] Questions about draft-ietf-radext-bigger-packets-03
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: <https://mailarchive.ietf.org/arch/browse/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: Thu, 29 Oct 2015 12:29:00 -0000

On Oct 29, 2015, at 7:36 AM, Stefan Winter <stefan.winter@restena.lu> wrote:
>>  On that note:  Response-Length is a  2-octet unsigned integer of maximum response length.
>> 
>>  Can that be changed to be of data type "integer"?   And maybe reference data types?
>> 
>>  I'll refresh the data types document today.
> 
> Unfortunately, RFC7120 does not foresee early allocation of "IESG
> Consensus" type allocations.

  I meant more that the draft should be updated to use "integer" instead of a non-standard data type.

> I wonder what is the document author's preference: publish the document
> without waiting for an implementation and the accompanying
> Implementation Status section?
> 
> Or include such a section, stating that a FreeRADIUS implementation is WIP?

  It's hard to have an implementation without an assigned packet code or attribute.  But I think I can put one together with reasonable values... and make sure to *not* ship before the numbers are allocated through IANA.

  Alan DeKok.