IETF Logo Mail Archive

Re: [AAA-DOCTORS] AAA AVP Code: who was/is the designated expert?

Benoit Claise <bclaise@cisco.com> Thu, 17 January 2013 09:03 UTC

Return-Path: <bclaise@cisco.com>
X-Original-To: aaa-doctors@ietfa.amsl.com
Delivered-To: aaa-doctors@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 22F5221F8839 for <aaa-doctors@ietfa.amsl.com>; Thu, 17 Jan 2013 01:03:20 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.586
X-Spam-Level:
X-Spam-Status: No, score=-10.586 tagged_above=-999 required=5 tests=[AWL=0.012, BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_HI=-8]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id jofiqX1+zYyn for <aaa-doctors@ietfa.amsl.com>; Thu, 17 Jan 2013 01:03:19 -0800 (PST)
Received: from av-tac-bru.cisco.com (weird-brew.cisco.com [144.254.15.118]) by ietfa.amsl.com (Postfix) with ESMTP id 19A2C21F87AB for <aaa-doctors@ietf.org>; Thu, 17 Jan 2013 01:03:18 -0800 (PST)
X-TACSUNS: Virus Scanned
Received: from strange-brew.cisco.com (localhost.cisco.com [127.0.0.1]) by av-tac-bru.cisco.com (8.13.8+Sun/8.13.8) with ESMTP id r0H93FMJ025124; Thu, 17 Jan 2013 10:03:15 +0100 (CET)
Received: from [10.60.67.84] (ams-bclaise-8913.cisco.com [10.60.67.84]) by strange-brew.cisco.com (8.13.8+Sun/8.13.8) with ESMTP id r0H92hYZ019473; Thu, 17 Jan 2013 10:02:54 +0100 (CET)
Message-ID: <50F7BE33.7030108@cisco.com>
Date: Thu, 17 Jan 2013 10:02:43 +0100
From: Benoit Claise <bclaise@cisco.com>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:17.0) Gecko/20130107 Thunderbird/17.0.2
MIME-Version: 1.0
To: "aaa-doctors@ietf.org" <aaa-doctors@ietf.org>
References: <50F52299.5000807@cisco.com>
In-Reply-To: <50F52299.5000807@cisco.com>
Content-Type: multipart/alternative; boundary="------------020103090303010406080104"
Cc: "dime-chairs@tools.ietf.org" <dime-chairs@tools.ietf.org>, "radext-chairs@tools.ietf.org" <radext-chairs@tools.ietf.org>
Subject: Re: [AAA-DOCTORS] AAA AVP Code: who was/is the designated expert?
X-BeenThere: aaa-doctors@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: AAA Doctors E-mail List <aaa-doctors.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/aaa-doctors>, <mailto:aaa-doctors-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/aaa-doctors>
List-Post: <mailto:aaa-doctors@ietf.org>
List-Help: <mailto:aaa-doctors-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/aaa-doctors>, <mailto:aaa-doctors-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 17 Jan 2013 09:03:20 -0000

Really, there were no AAA AVP code designated expert before Dan?

If the answer is no, then we need to find an expert.
Please send me proposals, even for yourself, in a private message.

Regards, Benoit
> Dear all,
>
> While asking the expert review for draft-ietf-dime-erp-16, IANA asked 
> Dan Romascanu.
> Indeed, Dan is listed as the expert at 
> http://www.iana.org/assignments/aaa-parameters/aaa-parameters.xml
>
>     AVP Codes
>         Registration Procedures
>             Expert Review with Specification
>         Experts
>             Dan Romascanu
>         Reference
>             [RFC6733]
>         Note
>             If more than 3 are needed, IETF Review.
>
> However,  Dan does not know exactly how he ended by being listed as 
> the designated expert for the AVP Codes registry for AAA.
> Probably a mistake while transitioning from RFC 3588 to RFC 6733, 
> because the IANA considerations for the AVP code has not changed, it 
> still requires Expert Review.
>
> If someone could shed some light on what happened, that would be perfect.
> Also, who was the expert before?
>
> Regards, Benoit

v2.23.0 | Report a Bug | By Email