IETF Logo Mail Archive

Re: [radext] Alissa Cooper's Discuss on draft-ietf-radext-ip-port-radius-ext-11: (with DISCUSS and COMMENT)

<lionel.morand@orange.com> Fri, 14 October 2016 15:16 UTC

Return-Path: <lionel.morand@orange.com>
X-Original-To: radext@ietfa.amsl.com
Delivered-To: radext@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 4850B12983C; Fri, 14 Oct 2016 08:16:21 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.619
X-Spam-Level:
X-Spam-Status: No, score=-2.619 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, FREEMAIL_FROM=0.001, RCVD_IN_DNSWL_LOW=-0.7, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_PASS=-0.001, UNPARSEABLE_RELAY=0.001] autolearn=ham autolearn_force=no
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 PFtb2M-Lkfxu; Fri, 14 Oct 2016 08:16:16 -0700 (PDT)
Received: from relais-inet.francetelecom.com (relais-ias91.francetelecom.com [193.251.215.91]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 9697E129523; Fri, 14 Oct 2016 08:16:16 -0700 (PDT)
Received: from omfedm08.si.francetelecom.fr (unknown [xx.xx.xx.4]) by omfedm12.si.francetelecom.fr (ESMTP service) with ESMTP id 9ED4C18C451; Fri, 14 Oct 2016 17:16:14 +0200 (CEST)
Received: from Exchangemail-eme2.itn.ftgroup (unknown [10.114.31.21]) by omfedm08.si.francetelecom.fr (ESMTP service) with ESMTP id 71F4E238059; Fri, 14 Oct 2016 17:16:14 +0200 (CEST)
Received: from OPEXCLILM43.corporate.adroot.infra.ftgroup ([fe80::ec23:902:c31f:731c]) by OPEXCLILM6C.corporate.adroot.infra.ftgroup ([fe80::d9f5:9741:7525:a199%18]) with mapi id 14.03.0319.002; Fri, 14 Oct 2016 17:16:14 +0200
From: lionel.morand@orange.com
To: Alan DeKok <aland@deployingradius.com>
Thread-Topic: [radext] Alissa Cooper's Discuss on draft-ietf-radext-ip-port-radius-ext-11: (with DISCUSS and COMMENT)
Thread-Index: AQHSCFDrJHPCcWo6q0uDplNMG5A9GKB3d+8HgDDR8KA=
Date: Fri, 14 Oct 2016 15:16:13 +0000
Message-ID: <32661_1476458174_5800F6BE_32661_2282_1_6B7134B31289DC4FAF731D844122B36E03D07880@OPEXCLILM43.corporate.adroot.infra.ftgroup>
References: <147137412687.22998.17081075232946825763.idtracker@ietfa.amsl.com> <CAHbuEH7+Gw=zDiN66Aydmie2M4dXcVqjLKWHixR7Qe6ECfN9Hg@mail.gmail.com> <D0152C61-D391-482B-BF1E-45180F89DA41@cooperw.in> <EACFFDF5-3974-4778-8EDD-A68410BAD972@gmail.com> <28413_1473165080_57CEB718_28413_354_4_6B7134B31289DC4FAF731D844122B36E01F9F38E@OPEXCLILM43.corporate.adroot.infra.ftgroup> <4DCE81CA-FC1F-4CFF-82E1-135E158087C6@deployingradius.com> <9128_1473174225_57CEDAD1_9128_1350_1_6B7134B31289DC4FAF731D844122B36E01F9F961@OPEXCLILM43.corporate.adroot.infra.ftgroup> <4B308285-584D-4A53-BCA0-F1EC1F9C3BC9@deployingradius.com> <1813_1473773040_57D7FDEF_1813_3639_1_6B7134B31289DC4FAF731D844122B36E01FAA8D8@OPEXCLILM43.corporate.adroot.infra.ftgroup> <23CAC502-C1F0-4DD6-AB82-8A38BD6D0B88@deployingradius.com>
In-Reply-To: <23CAC502-C1F0-4DD6-AB82-8A38BD6D0B88@deployingradius.com>
Accept-Language: fr-FR, en-US
Content-Language: fr-FR
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [10.168.234.5]
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-PMX-Version: 6.2.1.2478543, Antispam-Engine: 2.7.2.2107409, Antispam-Data: 2016.10.14.70315
Archived-At: <https://mailarchive.ietf.org/arch/msg/radext/1y2VWrhKKyrE_4i2vnoazob0rk0>
Cc: "draft-ietf-radext-ip-port-radius-ext@ietf.org" <draft-ietf-radext-ip-port-radius-ext@ietf.org>, "radext@ietf.org" <radext@ietf.org>, Alissa Cooper <alissa@cooperw.in>, "kathleen.moriarty.ietf@gmail.com" <kathleen.moriarty.ietf@gmail.com>, IESG <iesg@ietf.org>, "radext-chairs@ietf.org" <radext-chairs@ietf.org>
Subject: Re: [radext] Alissa Cooper's Discuss on draft-ietf-radext-ip-port-radius-ext-11: (with DISCUSS and COMMENT)
X-BeenThere: radext@ietf.org
X-Mailman-Version: 2.1.17
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: Fri, 14 Oct 2016 15:16:21 -0000

Hi Alan,

Can you elaborate a little bit?
What do you call 'appropriate parent TLV'?

If a registry is defined to track allocated value for sub-TLV, how to avoid collision if "All other TLV parents are free to specify whatever sub-TLVs they want".

Regards,

Lionel


> -----Message d'origine-----
> De : Alan DeKok [mailto:aland@deployingradius.com]
> Envoyé : mardi 13 septembre 2016 15:40
> À : MORAND Lionel IMT/OLN
> Cc : kathleen.moriarty.ietf@gmail.com; Alissa Cooper; draft-ietf-radext-ip-port-
> radius-ext@ietf.org; radext@ietf.org; IESG; radext-chairs@ietf.org
> Objet : Re: [radext] Alissa Cooper's Discuss on draft-ietf-radext-ip-port-radius-
> ext-11: (with DISCUSS and COMMENT)
> 
> 
> > On Sep 13, 2016, at 9:23 AM, <lionel.morand@orange.com>
> <lionel.morand@orange.com> wrote:
> > If such a registry is defined by the WG and managed by the IANA, to ensure
> that a newly-defined sub-TLV can be reused in any parent TLV,
> 
>   No.  Those sub-TLVs can only be re-used in *appropriate* parent TLVs.  The
> parents need to specify that they are using the common registry.  All other TLV
> parents are free to specify whatever sub-TLVs they want.
> 
>   Alan DeKok.


_________________________________________________________________________________________________________________________

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.

v2.23.0 | Report a Bug | By Email