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

Stefan Winter <stefan.winter@restena.lu> Thu, 29 October 2015 11:37 UTC

Return-Path: <stefan.winter@restena.lu>
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 BF8551B2D6E; Thu, 29 Oct 2015 04:37:01 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.909
X-Spam-Level:
X-Spam-Status: No, score=-1.909 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, T_RP_MATCHES_RCVD=-0.01, WEIRD_PORT=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 6HXUv746SaJO; Thu, 29 Oct 2015 04:36:59 -0700 (PDT)
Received: from smtprelay.restena.lu (smtprelay.restena.lu [158.64.1.62]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 5E3731B2D6B; Thu, 29 Oct 2015 04:36:59 -0700 (PDT)
Received: from aragorn.restena.lu (aragorn.restena.lu [IPv6:2001:a18:1:8::155]) by smtprelay.restena.lu (Postfix) with ESMTPS id 098C243AA0; Thu, 29 Oct 2015 12:36:58 +0100 (CET)
To: Alan DeKok <aland@deployingradius.com>
References: <55D57021.8060308@restena.lu> <183E3AC7-A5CB-43D4-ADCA-E0B7DD04B43C@deployingradius.com>
From: Stefan Winter <stefan.winter@restena.lu>
Openpgp: id=AD3091F3AB24E05F4F722C03C0DE6A358A39DC66; url=http://pgp.mit.edu:11371/pks/lookup?op=get&search=0xC0DE6A358A39DC66
X-Enigmail-Draft-Status: N1111
Message-ID: <563204D9.1010401@restena.lu>
Date: Thu, 29 Oct 2015 12:36:57 +0100
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:38.0) Gecko/20100101 Thunderbird/38.3.0
MIME-Version: 1.0
In-Reply-To: <183E3AC7-A5CB-43D4-ADCA-E0B7DD04B43C@deployingradius.com>
Content-Type: multipart/signed; micalg="pgp-sha512"; protocol="application/pgp-signature"; boundary="OQh1OvPpoGormtohgRbaScngxHPbK9KUo"
Archived-At: <http://mailarchive.ietf.org/arch/msg/radext/WcnBGiRTd-PSlv_K-CM8Glkc5y4>
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 11:37:01 -0000

Hello,

>> 5) For "Document quality", I would mention implementations which are
>> known to implement the spec. Are there any? If so, you may want to add
>> an RFC6982 "Implementation Status" section.
> 
>   Uh.... clickety click... I'll take a look at the implementation side of things. :)  But that requires IANA allocation of the packet code and attributes.
> 
>   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 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?

Greetings,

Stefan Winter

-- 
Stefan WINTER
Ingenieur de Recherche
Fondation RESTENA - Réseau Téléinformatique de l'Education Nationale et
de la Recherche
2, avenue de l'Université
L-4365 Esch-sur-Alzette

Tel: +352 424409 1
Fax: +352 422473

PGP key updated to 4096 Bit RSA - I will encrypt all mails if the
recipient's key is known to me

http://pgp.mit.edu:11371/pks/lookup?op=get&search=0xC0DE6A358A39DC66