Re: [radext] radius-fragmentation: New flag T field for the Long Extended Type

Alan DeKok <aland@deployingradius.com> Tue, 04 March 2014 15:33 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 7F09D1A0194 for <radext@ietfa.amsl.com>; Tue, 4 Mar 2014 07:33:51 -0800 (PST)
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 zt_SHIOSWMt3 for <radext@ietfa.amsl.com>; Tue, 4 Mar 2014 07:33:47 -0800 (PST)
Received: from power.freeradius.org (power.freeradius.org [88.190.25.44]) by ietfa.amsl.com (Postfix) with ESMTP id 5DC7E1A019D for <radext@ietf.org>; Tue, 4 Mar 2014 07:33:47 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by power.freeradius.org (Postfix) with ESMTP id E530D22400FF; Tue, 4 Mar 2014 16:33:43 +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 hQVv-dF4ZRjc; Tue, 4 Mar 2014 16:33:41 +0100 (CET)
Received: from dhcp-b41d.meeting.ietf.org (dhcp-b41d.meeting.ietf.org [31.133.180.29]) by power.freeradius.org (Postfix) with ESMTPSA id D0D0622400B6; Tue, 4 Mar 2014 16:33:41 +0100 (CET)
Message-ID: <5315F255.3050309@deployingradius.com>
Date: Tue, 04 Mar 2014 15:33:41 +0000
From: Alan DeKok <aland@deployingradius.com>
User-Agent: Thunderbird 2.0.0.24 (Macintosh/20100228)
MIME-Version: 1.0
To: lionel.morand@orange.com
References: <53107CBB.3020407@um.es> <53134D64.7080304@restena.lu> <53143367.6090001@um.es> <tsl61nvei02.fsf@mit.edu> <5314505E.3010200@deployingradius.com> <531452FC.6090704@um.es> <5314C5FE.3070403@deployingradius.com> <16313_1393946553_5315EFB9_16313_924_1_6B7134B31289DC4FAF731D844122B36E4DF643@PEXCVZYM13.corporate.adroot.infra.ftgroup>
In-Reply-To: <16313_1393946553_5315EFB9_16313_924_1_6B7134B31289DC4FAF731D844122B36E4DF643@PEXCVZYM13.corporate.adroot.infra.ftgroup>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Archived-At: http://mailarchive.ietf.org/arch/msg/radext/kZbP8qwqUhro1kFW3Sw2r9eIiAU
Cc: Sam Hartman <hartmans@painless-security.com>, Stefan Winter <stefan.winter@restena.lu>, Alejandro Perez Mendez <alex@um.es>, "radext@ietf.org" <radext@ietf.org>
Subject: Re: [radext] radius-fragmentation: New flag T field for the Long Extended Type
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: <http://www.ietf.org/mail-archive/web/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: Tue, 04 Mar 2014 15:33:51 -0000

lionel.morand@orange.com wrote:
> The question is simple: how do we ensure that another draft will not allocate the same 2nd bit to another feature? It would mean that the same Long-extended-type attribute would have two possible interpretations/process...

  I think we're safe with manual tracking.  I don't see any other draft
allocating the same bit.

> Are we only relying on living memories? :)

  The documents are available on a public web page as part of the RFC
process.

> Maybe we don't care because it is an experimental document... or maybe this doc will update the RFC6929 to indicate that the 2nd bit is used for "T".

  We can't have an experimental draft update a standards track document.

  Alan DeKok.