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

<lionel.morand@orange.com> Tue, 04 March 2014 15:22 UTC

Return-Path: <lionel.morand@orange.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 697541A0085 for <radext@ietfa.amsl.com>; Tue, 4 Mar 2014 07:22:42 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.899
X-Spam-Level:
X-Spam-Status: No, score=-1.899 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, FREEMAIL_FROM=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001, UNPARSEABLE_RELAY=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 EYnJPCfQBDzm for <radext@ietfa.amsl.com>; Tue, 4 Mar 2014 07:22:37 -0800 (PST)
Received: from relais-inet.francetelecom.com (relais-ias244.francetelecom.com [80.12.204.244]) by ietfa.amsl.com (Postfix) with ESMTP id 708EE1A005E for <radext@ietf.org>; Tue, 4 Mar 2014 07:22:37 -0800 (PST)
Received: from omfeda08.si.francetelecom.fr (unknown [xx.xx.xx.201]) by omfeda11.si.francetelecom.fr (ESMTP service) with ESMTP id B2DD71B8185; Tue, 4 Mar 2014 16:22:33 +0100 (CET)
Received: from Exchangemail-eme1.itn.ftgroup (unknown [10.114.1.186]) by omfeda08.si.francetelecom.fr (ESMTP service) with ESMTP id 8E41338412D; Tue, 4 Mar 2014 16:22:33 +0100 (CET)
Received: from PEXCVZYM13.corporate.adroot.infra.ftgroup ([fe80::cc7e:e40b:42ef:164e]) by PEXCVZYH01.corporate.adroot.infra.ftgroup ([::1]) with mapi id 14.03.0174.001; Tue, 4 Mar 2014 16:22:33 +0100
From: <lionel.morand@orange.com>
To: Alan DeKok <aland@deployingradius.com>, Alejandro Perez Mendez <alex@um.es>
Thread-Topic: [radext] radius-fragmentation: New flag T field for the Long Extended Type
Thread-Index: AQHPNH4c8tS+HG09uUOJ1wR0Fs0aSJrN3YMAgAESMoCAADD37v//8ZAAgAADHwCAAIkaAIABb9YA
Date: Tue, 4 Mar 2014 15:22:31 +0000
Message-ID: <16313_1393946553_5315EFB9_16313_924_1_6B7134B31289DC4FAF731D844122B36E4DF643@PEXCVZYM13.corporate.adroot.infra.ftgroup>
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>
In-Reply-To: <5314C5FE.3070403@deployingradius.com>
Accept-Language: fr-FR, en-US
Content-Language: fr-FR
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [10.197.38.3]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-PMX-Version: 6.0.3.2322014, Antispam-Engine: 2.7.2.2107409, Antispam-Data: 2013.11.19.63615
Archived-At: http://mailarchive.ietf.org/arch/msg/radext/3GCYr8sNyZA6tziiBl1N1FRdByw
Cc: Sam Hartman <hartmans@painless-security.com>, Stefan Winter <stefan.winter@restena.lu>, "radext@ietf.org" <radext@ietf.org>
Subject: [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:22:42 -0000

I repeat my comment raised during the meeting. 

RFC6929 (Std) allocates the first bit after the Extended-Type field to the (M)ore and the rest (7-bit) is put as reserved.
But there is nothing about how to allocate the remaining reserved bits.

This draft allocates the second bit to (T)runcation.

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

Are we only relying on living memories? :)
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".

It is not an issue with the current draft. Just an administrative issue.

Regards,

Lionel

_________________________________________________________________________________________________________________________

Ce message et ses pieces jointes peuvent contenir des informations confidentielles ou privilegiees et ne doivent donc
pas etre diffuses, exploites ou copies sans autorisation. Si vous avez recu ce message par erreur, veuillez le signaler
a l'expediteur et le detruire ainsi que les pieces jointes. Les messages electroniques etant susceptibles d'alteration,
Orange decline toute responsabilite si ce message a ete altere, deforme ou falsifie. Merci.

This message and its attachments may contain confidential or privileged information that may be protected by law;
they should not be distributed, used or copied without authorisation.
If you have received this email in error, please notify the sender and delete this message and its attachments.
As emails may be altered, Orange is not liable for messages that have been modified, changed or falsified.
Thank you.