Re: [radext] Proposed new charter text

Peter Deacon <peterd@iea-software.com> Sun, 22 March 2015 19:35 UTC

Return-Path: <peterd@iea-software.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 A729E1A0AFE for <radext@ietfa.amsl.com>; Sun, 22 Mar 2015 12:35:36 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.511
X-Spam-Level:
X-Spam-Status: No, score=-0.511 tagged_above=-999 required=5 tests=[BAYES_05=-0.5, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01] 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 vtUTTCbroChs for <radext@ietfa.amsl.com>; Sun, 22 Mar 2015 12:35:35 -0700 (PDT)
Received: from aspen.iea-software.com (www.iea-software.com [70.89.142.193]) by ietfa.amsl.com (Postfix) with ESMTP id 3E5F01A0A85 for <radext@ietf.org>; Sun, 22 Mar 2015 12:35:35 -0700 (PDT)
Received: from SMURF.peterd.ws (unverified [10.0.3.195]) by aspen.iea-software.com (Rockliffe SMTPRA 7.0.6) with ESMTP id <B0005964295@aspen.iea-software.com>; Sun, 22 Mar 2015 12:35:34 -0700
Date: Sun, 22 Mar 2015 12:35:39 -0700
From: Peter Deacon <peterd@iea-software.com>
To: Stefan Winter <stefan.winter@restena.lu>
In-Reply-To: <5502B836.5000100@restena.lu>
Message-ID: <alpine.WNT.2.20.1.1503221133420.3600@SMURF>
References: <5502B836.5000100@restena.lu>
User-Agent: Alpine 2.20.1 (WNT 67 2015-01-07)
MIME-Version: 1.0
Content-Type: text/plain; CHARSET="US-ASCII"; FORMAT="flowed"
Content-ID: <alpine.WNT.2.20.1.1503221152221.3600@SMURF>
Archived-At: <http://mailarchive.ietf.org/arch/msg/radext/IZRXbQA3aisc3hTQrWHyOE_sggg>
Cc: "radext@ietf.org" <radext@ietf.org>
Subject: Re: [radext] Proposed new charter text
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: Sun, 22 Mar 2015 19:35:36 -0000

On Fri, 13 Mar 2015, Stefan Winter wrote:

> as you may recall, we discussed new charter text at IETF91, which was
> unanimously accepted in the room.

> We still need to verify consensus on the list, so below is the proposed
> updated charter text. This mail starts a two week comment period on the
> charter text. Please send your comments to the list until 2015-03-27
> 2400 UTC.

> - CoA proxying.  RFC 5176 permits proxying of CoA and Disconnect
> messages, but makes no provisions for how that is done in a roaming
> environment.  This work item will provide descriptions of how to use the
> Operator-Name attribute in a roaming environment to proxy CoA packets.
> It will also define a new attribute which defines an opaque NAS
> identifier which can be used to uniquely identify a visited NAS, and
> whose value will not be modified when proxying, as is done with
> NAS-Identifier and NAS-IP-Address.

Recommend following text:

- CoA proxying.  RFC 5176 permits proxying of CoA and Disconnect messages, 
but makes no provisions for how that is done in a roaming environment. 
This work item will provide descriptions of how to proxy Dynamic 
Authorization messages using realm based proxy.  It will also define a new 
attribute to assist the visited network in processing and forwarding 
Dynamic Authorization requests to appropriate NAS.

While I generally support approach and associated draft 
draft-dekok-radext-coa-proxy-00.txt have some concerns and would prefer to 
keep some prescriptive details out of the charter.

regards,
Peter