FW: BOUNCE aaa-doctors@ops.ietf.org: Admin request of type /^ \s*approve\b/i at line 9

["Wijnen, Bert (Bert)" <bwijnen@lucent.com>]

Approved bwloss
From dromasca@avaya.com Mon May 22 19:25:55 2006
X-Spam-Checker-Version: SpamAssassin 3.1.1 (2006-03-10) on psg.com
X-Spam-Level: 
X-Spam-Status: No, score=-2.6 required=5.0 tests=AWL,BAYES_00 autolearn=ham 
	version=3.1.1
Received: from [198.152.13.103] (helo=co300216-ier2.net.avaya.com)
	by psg.com with esmtps (TLSv1:DES-CBC3-SHA:168)
	(Exim 4.60 (FreeBSD))
	(envelope-from <dromasca@avaya.com>)
	id 1FiG2N-0006M6-C3
	for aaa-doctors@ops.ietf.org; Mon, 22 May 2006 19:25:55 +0000
Received: from IS0004AVEXU1.global.avaya.com (h135-64-105-51.avaya.com [135.64.105.51])
	by co300216-ier2.net.avaya.com (Switch-3.1.8/Switch-3.1.7) with ESMTP id k4MJOSuo028764
	for <aaa-doctors@ops.ietf.org>; Mon, 22 May 2006 15:24:29 -0400
content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Subject: FW: Designated Expert for Radius (RFC3575)
X-MimeOLE: Produced By Microsoft Exchange V6.0.6603.0
Date: Mon, 22 May 2006 22:25:52 +0300
Message-ID: <AAB4B3D3CF0F454F98272CBE187FDE2F0A886618@is0004avexu1.global.avaya.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: Designated Expert for Radius (RFC3575)
Thread-Index: AcZoY1TG4b3OcJzoQRmcMEDgwgb/MQCjqBJwBLVMcMAAA2SSwA==
From: "Romascanu, Dan \(Dan\)" <dromasca@avaya.com>
To: "David Kessens" <david.kessens@nokia.com>, <dnelson@enterasys.com>,
        "Bernard Aboba" <aboba@internaut.com>
Cc: "Aaa-Doctors \(E-mail\)" <aaa-doctors@ops.ietf.org>,
        "Bert Wijnen" <bwijnen@lucent.com>
X-Scanner: InterScan AntiVirus for Sendmail

 I believe that we said that the RADEXT WG can help in identifying a
volunteer to fill in this job, on the lines of what is being defined by
RFC 3575.=20

   For registration requests where a Designated Expert should be
   consulted, the responsible IESG area director should appoint the
   Designated Expert.  The intention is that any allocation will be
   accompanied by a published RFC.  However, the Designated Expert can
   approve allocations once it seems clear that an RFC will be
   published, allowing for the allocation of values prior to the
   document being approved for publication as an RFC.  The Designated
   Expert will post a request to the AAA WG mailing list (or a successor
   designated by the Area Director) for comment and review, including an
   Internet-Draft. =20

This expert can act as a focal point of interfacing between IANA and the
AAA Doctors list.=20

Dan

=20

-----Original Message-----
From: Michelle Cotton [mailto:michelle.cotton@icann.org]=20
Sent: Monday, May 22, 2006 8:44 PM
To: iesg@ietf.org
Cc: 'Yoshiko Chong'
Subject: RE: Designated Expert for Radius (RFC3575)

Brian/IESG:

Did I miss a message on an expert appointment?  Just checking to see if
an expert has been approved for RADIUS.

Thanks in advance,

Michelle Cotton
IANA


-----Original Message-----
From: Michelle Cotton [mailto:michelle.cotton@icann.org]
Sent: Friday, April 28, 2006 11:32 AM
To: 'Brian E Carpenter'
Cc: 'iesg@ietf.org'; 'Yoshiko Chong'
Subject: RE: Designated Expert for Radius (RFC3575)

Brian,

I don't believe it did.....can you assist in getting an answer?

Thank you,

Michelle
IANA


-----Original Message-----
From: Brian E Carpenter [mailto:brc@zurich.ibm.com]
Sent: Tuesday, April 25, 2006 5:21 AM
To: Michelle Cotton
Cc: iesg@ietf.org; 'Yoshiko Chong'
Subject: Re: Designated Expert for Radius (RFC3575)

Did this get answered?

     Brian


Michelle Cotton wrote:
> IESG:
>=20
> The IANA currently has 2 requests to add attribute values to existing
Radius
> types.
>=20
> The registration rules are currently as follows:
>=20
>    Certain attributes (for example, NAS-Port-Type) in RADIUS define a
>    list of values to correspond with various meanings.  There can be 4
>    billion (2^32) values for each attribute.  Additional values can be
>    allocated by the Designated Expert.  The exception to this policy
is
>    the Service-Type attribute (6), whose values define new modes of
>    operation for RADIUS.  Values 1-16 of the Service-Type attribute
have
>    been allocated.  Allocation of new Service-Type values are by IETF
>    Consensus.  The intention is that any allocation will be
accompanied
>    by a published RFC.
>=20
> Has an expert been designated for Radius?
>=20
> We would also like to verify with the expert, once designated, that=20
> the information on the Matrix for Radius is correct and that no=20
> corrections
need
> to be made.
>=20
> Thanks in advance.
>=20
> Michelle Cotton
> IANA
>=20
>=20
>=20
>=20