Alice Russo <arusso@amsl.com> · Tue, 4 Dec 2012 12:05:25 -0500

RFC 3575 Section 2.1 states the following:
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.
Note that the Tunnel-Type and Tunnel-Medium-Type attributes are not called out as an exception, only Service-Type.
If the intent was to exempt RFC 2868, those attributes would have been included as exceptions but they are not.
Therefore, it looks to me like the omission of RFC 2868 in the Updates: header is an errata.
	This document updates RFC 2865.
	This document updates RFC 2865 and RFC 2868.
6.1.  Tunnel-Type Attribute Values

   Values 1-12 of the Tunnel-Type Attribute are defined in Section 5.1;
   the remaining values are available for assignment by the IANA with
   IETF Consensus [16].

6.2.  Tunnel-Medium-Type Attribute Values

   Values 1-15 of the Tunnel-Medium-Type Attribute are defined in
   Section 5.2; the remaining values are available for assignment by the
   IANA with IETF Consensus [16].
   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.
6.1.  Tunnel-Type Attribute Values

   Values 1-12 of the Tunnel-Type Attribute are defined in Section 5.1;
   the remaining values are available for assignment by the IANA with
   IETF Consensus [16].

6.2.  Tunnel-Medium-Type Attribute Values

   Values 1-15 of the Tunnel-Medium-Type Attribute are defined in
   Section 5.2; the remaining values are available for assignment by the
   IANA with IETF Consensus [16].
   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.
_______________________________________________
AAA-DOCTORS mailing list
AAA-DOCTORS@ietf.org
https://www.ietf.org/mailman/listinfo/aaa-doctors

FYI, the source data for RFC 3575 has been corrected to IETF NON WORKING GROUP. It was incorrectly marked as Independent upon being added to the RFC Editor queue in 2003. We have notified the Secretariat so the datatracker will show the corrected document stream.

Thank you.
RFC Editor/ar

On Dec 4, 2012, at 10:12 AM, I wrote:

> Regarding the source of RFC 3575, I will check with the team about whether it should be corrected from Independent to IETF NON-WG based on the Protocol Action message from 2003 (http://www.ietf.org/mail-archive/web-old/ietf-announce-old/current/msg23959.html):
> 
>> The IESG has approved the Internet-Draft 'IANA Considerations for
>> RADIUS' <draft-aboba-radius-iana-07.txt> as a Proposed Standard.
>> This has been reviewed in the IETF but is not the product of an
>> IETF Working Group.
>> 
> (For the purposes of errata review, the area assignment would be ops.)

6.1.  Tunnel-Type Attribute Values

   Values 1-12 of the Tunnel-Type Attribute are defined in Section 5.1;
   the remaining values are available for assignment by the IANA with
   IETF Consensus [16].

6.2.  Tunnel-Medium-Type Attribute Values

   Values 1-15 of the Tunnel-Medium-Type Attribute are defined in
   Section 5.2; the remaining values are available for assignment by the
   IANA with IETF Consensus [16].
   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.
_______________________________________________
AAA-DOCTORS mailing list
AAA-DOCTORS@ietf.org
https://www.ietf.org/mailman/listinfo/aaa-doctors

_______________________________________________
AAA-DOCTORS mailing list
AAA-DOCTORS@ietf.org
https://www.ietf.org/mailman/listinfo/aaa-doctors

A new version (-08) has been submitted for draft-ietf-softwire-6rd-radius-attrib:
http://www.ietf.org/internet-drafts/draft-ietf-softwire-6rd-radius-attrib-08.txt

Sub state has been changed to AD Followup from Revised ID Needed

The IETF datatracker page for this Internet-Draft is:
https://datatracker.ietf.org/doc/draft-ietf-softwire-6rd-radius-attrib/

Diff from previous version:
http://www.ietf.org/rfcdiff?url2=draft-ietf-softwire-6rd-radius-attrib-08

IETF Secretariat.

Your authorization is required for a mailing list subscription request
approval:

    For:  yuankui.zhao@gmail.com
    List: aaa-doctors@ietf.org

At your convenience, visit:

    https://www.ietf.org/mailman/admindb/aaa-doctors

to process the request.

A new version (-08) has been submitted for draft-ietf-softwire-6rd-rad=
ius-attrib:
http://www.ietf.org/inter=
net-drafts/draft-ietf-softwire-6rd-radius-attrib-08.txt

Sub state has been changed to AD Followup from Revised ID Needed

The IETF datatracker page for this Internet-Draft is:
https://datatracker.ietf.org/doc/d=
raft-ietf-softwire-6rd-radius-attrib/

Diff from previous version:
http://www.ietf.org/rfcdiff?ur=
l2=3Ddraft-ietf-softwire-6rd-radius-attrib-08

IETF Secretariat.

A new version (-08) has been submitted for=
 draft-ietf-softwire-6rd-radius-attrib:
http://www.ietf.org/internet-drafts/draft-iet=
f-softwire-6rd-radius-attrib-08.txt

Sub state has been changed to AD Followup =
from Revised ID Needed

The IETF datatracker page for this Interne=
t-Draft is:
https://datatracker.ietf.org/doc/draft-ietf-softwire-6=
rd-radius-attrib/

Diff from previous version:
http://www.ietf.org/rfcdiff?url2=3Ddraft-ietf-soft=
wire-6rd-radius-attrib-08

IETF Secretariat.

A new version (-08) has been submitted for=
 draft-ietf-softwire-6rd-radius-attrib:
http://www.ietf.org/internet-drafts/draft-iet=
f-softwire-6rd-radius-attrib-08.txt

Sub state has been changed to AD Followup =
from Revised ID Needed

The IETF datatracker page for this Interne=
t-Draft is:
https://datatracker.ietf.org/doc/draft-ietf-softwire-6=
rd-radius-attrib/

Diff from previous version:
http://www.ietf.org/rfcdiff?url2=3Ddraft-ietf-soft=
wire-6rd-radius-attrib-08

IETF Secretariat.

Subject:	Re: Informal telechat: RFC3575 errata, "IANA Considerations for RADIUS (Remote Authentication Dial In User Service)"
Date:	Tue, 4 Dec 2012 12:05:25 -0500
From:	Alice Russo <arusso@amsl.com>
To:	Benoit Claise <bclaise@cisco.com>
CC:	Bernard Aboba <Bernard.Aboba@microsoft.com>, RFC Editor <rfc-editor@rfc-editor.org>, ISE <rfc-ise@rfc-editor.org>

Subject:	New Version Notification - draft-ietf-softwire-6rd-radius-attrib-08.txt
Date:	Sun, 09 Dec 2012 23:15:03 -0800
From:	internet-drafts@ietf.org
To:	softwire-chairs@tools.ietf.org, draft-ietf-softwire-6rd-radius-attrib@tools.ietf.org, rdroms.ietf@gmail.com, adrian@olddog.co.uk, bclaise@cisco.com, turners@ieca.com

Subject:	Re: New subscription request to list AAA-DOCTORS from yuankui.zhao@gmail.com
Date:	Sun, 9 Dec 2012 12:33:24 +0800
From:	john.zhao <yuankui.zhao@gmail.com>
To:	Benoit Claise <bclaise@cisco.com>

Subject:	New subscription request to list AAA-DOCTORS from yuankui.zhao@gmail.com
Date:	Fri, 07 Dec 2012 02:38:31 -0800
From:	aaa-doctors-owner@ietf.org
To:	aaa-doctors-owner@ietf.org

Subject:	New Version Notification - draft-ietf-softwire-6rd-radius-attrib-08.txt=
Date:	Sun, 09 Dec 2012 23:15:03 -0800
From:	internet-drafts@ietf.org
To:	softwire-chairs@tools.ietf.org, draft-ietf-softwire-6rd-radius-attrib@tools.ietf.org, rdroms.ietf@gmail.com, adrian@olddog.co.uk, bclaise@cisco.com, turners@ieca.com

Subject:	New Version Notification - draft-ietf-softwire-6rd-rad= ius-attrib-08.txt
Date:	Sun, 09 Dec 2012 23:15:03 -0800
From:	internet-drafts@ietf.org
To:	softwire-chairs@tools.iet= f.org, draft-ietf-softwire-6rd-radius-attrib@= tools.ietf.org, rdroms.ietf@gmail.com, adrian@olddog.co.uk, bclaise@cisco.com, turners@iec= a.com