Re: [radext] Extended IDs

Peter Deacon <peterd@iea-software.com> Wed, 13 December 2017 08:21 UTC

Return-Path: <peterd@iea-software.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 457F31275FD for <radext@ietfa.amsl.com>; Wed, 13 Dec 2017 00:21:45 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.901
X-Spam-Level:
X-Spam-Status: No, score=-1.901 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_PASS=-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 tmhkscebvEbR for <radext@ietfa.amsl.com>; Wed, 13 Dec 2017 00:21:43 -0800 (PST)
Received: from aspen.iea-software.com (www.iea-software.com [70.89.142.193]) by ietfa.amsl.com (Postfix) with ESMTP id 3867212700F for <radext@ietf.org>; Wed, 13 Dec 2017 00:21:43 -0800 (PST)
Received: from smurf (unverified [10.0.3.195]) by aspen.iea-software.com (Rockliffe SMTPRA 7.0.6) with ESMTP id <B0006062075@aspen.iea-software.com>; Wed, 13 Dec 2017 00:21:42 -0800
Date: Wed, 13 Dec 2017 00:21:46 -0800
From: Peter Deacon <peterd@iea-software.com>
To: Enke Chen <enkechen@cisco.com>
cc: "Naiming Shen (naiming)" <naiming@cisco.com>, "radext@ietf.org" <radext@ietf.org>
In-Reply-To: <d930039b-53ed-78fa-2d10-b33f86cfa751@cisco.com>
Message-ID: <alpine.WNT.2.21.1.1712122357400.2252@smurf>
References: <fef698a5-9802-c9be-04d7-1e869651c988@restena.lu> <dfd0ff02-c9e8-7253-4fb4-1e6def3e93b2@restena.lu> <933E6F70-A7C1-4168-9AC9-F925EF78D9E2@jisc.ac.uk> <AE2036D0-1294-45B5-A0D7-16F91E0B4248@cisco.com> <alpine.WNT.2.21.1.1712121615090.2252@smurf> <EE3BB1A7-EAD9-4BE1-9EA2-B780580E5C95@cisco.com> <alpine.WNT.2.21.1.1712121704430.2252@smurf> <B41EF4CD-309C-4E0F-BE7A-B77A244DA421@cisco.com> <alpine.WNT.2.21.1.1712121824110.2252@smurf> <313FEFCE-FD61-4394-804D-91BAE98CA687@cisco.com> <alpine.WNT.2.21.1.1712121947300.2252@smurf> <38A550CE-C1E5-441E-B25E-7E87D266F627@cisco.com> <alpine.WNT.2.21.1.1712122230570.2252@smurf> <551F795A-7385-401F-881A-EB46C9242DCC@cisco.com> <alpine.WNT.2.21.1.1712122307550.2252@smurf> <d930039b-53ed-78fa-2d10-b33f86cfa751@cisco.com>
User-Agent: Alpine 2.21.1 (WNT 202 2017-01-01)
MIME-Version: 1.0
Content-Type: text/plain; format="flowed"; charset="US-ASCII"
Archived-At: <https://mailarchive.ietf.org/arch/msg/radext/COwGxy3KA1fr4cjY4Ymhrg0wkXU>
Subject: Re: [radext] Extended IDs
X-BeenThere: radext@ietf.org
X-Mailman-Version: 2.1.22
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: Wed, 13 Dec 2017 08:21:45 -0000

On Tue, 12 Dec 2017, Enke Chen wrote:

> The "Status-Server" is used for capability negotiation by both drafts.

Completely agree.  None of my comments regarding status server are unique 
to either draft.

> Neither mechanism will work with an ancient server that does not support 
> the "Status-server" properly.

This is not my understanding.  I see nothing in text precluding anyone 
from manually configuring support for extended-id or ORA and never using 
status-server if they prefer not to for whatever reason.

Welcome specific citation saying I'm wrong or logical argument explaining 
why extended-id is not possible without status-server /w relevant 
citations.  Opinions of usefulness of status-server for capability 
negotiation NOT welcome.

What's the point of explicitly referencing the possibility of manual 
enablement if not to support extended-id without status-server?

"  Unless specified by configuration, a client MUST NOT send a RADIUS
    packet (other than the Status-Server request) with the "Extended
    Identifier Attribute" to a server until it has received a response
    from the server confirming its support for the Extended Identifier
    feature using the "Extended Identifier Attribute"."

regards,
Peter