One document matched: draft-zorn-dime-rfc4005bis-01.xml
<?xml version="1.0" encoding="UTF-8"?>
<?xml-stylesheet type='text/xsl' href='http://xml.resource.org/authoring/rfc2629.xslt' ?>
<!DOCTYPE rfc SYSTEM "rfc2629.dtd" [
<!ENTITY I-D.ietf-dime-rfc3588bis PUBLIC "" "http://xml.resource.org/public/rfc/bibxml3/reference.I-D.ietf-dime-rfc3588bis.xml">
<!ENTITY rfc3539 PUBLIC "" "http://xml.resource.org/public/rfc/bibxml/reference.RFC.3539.xml">
<!ENTITY rfc2865 PUBLIC "" "http://xml.resource.org/public/rfc/bibxml/reference.RFC.2865.xml">
<!ENTITY rfc4072 PUBLIC "" "http://xml.resource.org/public/rfc/bibxml/reference.RFC.4072.xml">
<!ENTITY rfc2881 PUBLIC "" "http://xml.resource.org/public/rfc/bibxml/reference.RFC.2881.xml">
<!ENTITY rfc2989 PUBLIC "" "http://xml.resource.org/public/rfc/bibxml/reference.RFC.2989.xml">
<!ENTITY rfc1661 PUBLIC "" "http://xml.resource.org/public/rfc/bibxml/reference.RFC.1661.xml">
<!ENTITY rfc1334 PUBLIC "" "http://xml.resource.org/public/rfc/bibxml/reference.RFC.1334.xml">
<!ENTITY rfc1994 PUBLIC "" "http://xml.resource.org/public/rfc/bibxml/reference.RFC.1994.xml">
<!ENTITY rfc3169 PUBLIC "" "http://xml.resource.org/public/rfc/bibxml/reference.RFC.3169.xml">
<!ENTITY rfc3162 PUBLIC "" "http://xml.resource.org/public/rfc/bibxml/reference.RFC.3162.xml">
<!ENTITY rfc3516 PUBLIC "" "http://xml.resource.org/public/rfc/bibxml/reference.RFC.3516.xml">
<!ENTITY rfc5226 PUBLIC "" "http://xml.resource.org/public/rfc/bibxml/reference.RFC.5226.xml">
<!ENTITY rfc2119 PUBLIC "" "http://xml.resource.org/public/rfc/bibxml/reference.RFC.2119.xml">
<!ENTITY rfc2866 PUBLIC "" "http://xml.resource.org/public/rfc/bibxml/reference.RFC.2866.xml">
<!ENTITY rfc2869 PUBLIC "" "http://xml.resource.org/public/rfc/bibxml/reference.RFC.2869.xml">
<!ENTITY rfc2868 PUBLIC "" "http://xml.resource.org/public/rfc/bibxml/reference.RFC.2868.xml">
<!ENTITY rfc2867 PUBLIC "" "http://xml.resource.org/public/rfc/bibxml/reference.RFC.2867.xml">
<!ENTITY rfc3575 PUBLIC "" "http://xml.resource.org/public/rfc/bibxml/reference.RFC.3575.xml">
<!ENTITY rfc4004 PUBLIC "" "http://xml.resource.org/public/rfc/bibxml/reference.RFC.4004.xml">
<!ENTITY rfc3580 PUBLIC "" "http://xml.resource.org/public/rfc/bibxml/reference.RFC.3580.xml">
<!ENTITY rfc2474 PUBLIC "" "http://xml.resource.org/public/rfc/bibxml/reference.RFC.2474.xml">
<!ENTITY rfc2597 PUBLIC "" "http://xml.resource.org/public/rfc/bibxml/reference.RFC.2597.xml">
<!ENTITY rfc2661 PUBLIC "" "http://xml.resource.org/public/rfc/bibxml/reference.RFC.2661.xml">
<!ENTITY rfc1990 PUBLIC "" "http://xml.resource.org/public/rfc/bibxml/reference.RFC.1990.xml">
<!ENTITY rfc2637 PUBLIC "" "http://xml.resource.org/public/rfc/bibxml/reference.RFC.2637.xml">
<!ENTITY rfc3246 PUBLIC "" "http://xml.resource.org/public/rfc/bibxml/reference.RFC.3246.xml">
<!ENTITY rfc2548 PUBLIC "" "http://xml.resource.org/public/rfc/bibxml/reference.RFC.2548.xml">
]>
<?rfc strict="yes"?>
<?rfc comments="no"?>
<?rfc inline="yes"?>
<?rfc editing="no"?>
<?rfc toc="yes"?>
<?rfc tocompact="yes"?>
<?rfc tocdepth="5"?>
<?rfc symrefs="yes"?>
<?rfc sortrefs="yes"?>
<?rfc compact="yes"?>
<?rfc subcompact="no"?>
<?rfc rfcedstyle="yes"?>
<?rfc rfcprocack="no"?>
<?rfc tocindent="yes"?>
<rfc category="std" obsoletes="RFC4005" docName="draft-zorn-dime-rfc4005bis-01" ipr="trust200902">
<front>
<title abbrev="Diameter NASREQ">Diameter Network Access Server Application</title>
<author fullname="Glen Zorn" initials="G." surname="Zorn" role="editor">
<organization>Network Zen</organization>
<address>
<postal>
<street>1463 East Republican Street</street>
<street>#358</street>
<city>Seattle</city>
<region>Washington</region>
<code>98112</code>
<country>USA</country>
</postal>
<email>gwz@net-zen.net</email>
</address>
</author>
<date year="2010"/>
<abstract>
<t>
This document describes the Diameter protocol application used for
Authentication, Authorization, and Accounting (AAA) services in the
Network Access Server (NAS) environment. When combined with the
Diameter Base protocol, Transport Profile, and Extensible
Authentication Protocol specifications, this application
specification satisfies typical network access services requirements.
</t>
</abstract>
</front>
<middle>
<section title="Introduction">
<t>
This document describes the Diameter protocol application used for
AAA in the Network Access Server (NAS) environment. When combined
with the Diameter Base protocol <xref target="I-D.ietf-dime-rfc3588bis"/>,
Transport Profile <xref target="RFC3539"/>,
and EAP
<xref target="RFC4072"/>
specifications, this specification satisfies NAS-related requirements defined
in <xref target="RFC2989"/>
and <xref target="RFC3169"/>.
<vspace blankLines="1"/>
First, this document describes the operation of a Diameter NAS
application. Then it defines the Diameter message Command-Codes.
The following sections list the AVPs used in these messages, grouped
by common usage. These are session identification, authentication,
authorization, tunneling, and accounting. The authorization AVPs are
further broken down by service type.
</t>
<section title="Terminology">
<t>
Section 1.2 of the base Diameter specification <xref target="I-D.ietf-dime-rfc3588bis"/>
defines most of
the terminology used in this document. Additionally, the following
terms and acronyms are used in this application:
<list style="hanging">
<t hangText="NAS (Network Access Server)">
<vspace blankLines="0"/>
A device that provides an access
service for a user to a network. The service may be a network
connection or a value-added service such as terminal emulation <xref target="RFC2881"/>.
</t>
<t hangText="PPP (Point-to-Point Protocol)">
<vspace blankLines="0"/>
A multiprotocol serial datalink.
PPP is the primary IP datalink used for dial-in
NAS connection service <xref target="RFC1661"/>.
</t>
<t hangText="CHAP (Challenge Handshake Authentication Protocol)">
<vspace blankLines="0"/>
An authentication process used in PPP <xref target="RFC1994"/>.
</t>
<t hangText="PAP (Password Authentication Protocol)">
<vspace blankLines="0"/>
A deprecated PPP authentication process,
but often used for backward compatibility <xref target="RFC1334"/>.
</t>
<t hangText="SLIP (Serial Line Interface Protocol)">
<vspace blankLines="0"/>
A serial datalink that only supports IP. A design prior to PPP.
</t>
<t hangText="ARAP (Appletalk Remote Access Protocol)">
<vspace blankLines="0"/>
A serial datalink for accessing Appletalk networks <xref target="ARAP"/>.
</t>
<t hangText="IPX (Internet Packet Exchange)">
<vspace blankLines="0"/>
The network protocol used by NetWare networks <xref target="IPX"/>.
</t>
<t hangText="LAT (Local Area Transport">
<vspace blankLines="0"/>
A Digital Equipment Corp. LAN protocol for terminal services <xref target="LAT"/>.
</t>
<t hangText="VPN (Virtual Private Network)">
<vspace blankLines="0"/>
In this document, this term is used to describe access services that use tunneling methods.
</t>
</list>
</t>
</section>
<section title="Requirements Language">
<t>
In this document, the key words "MAY", "MUST", "MUST NOT", "OPTIONAL",
"RECOMMENDED", "SHOULD", and "SHOULD NOT" are to be interpreted
as described in <xref target="RFC2119"/>,
</t>
</section>
<section title="Advertising Application Support" anchor="A-A-S">
<t>
Diameter applications conforming to this specification MUST advertise
support by including the value of one (1) in the Auth-Application-Id
of the Capabilities-Exchange-Request (CER), AA-Request (AAR), and AA-Answer (AAA)
messages. All other messages are defined by RFC 3588
and use the Base application id value.
</t>
</section>
</section>
<section title="NAS Calls, Ports, and Sessions">
<t>
The arrival of a new call or service connection at a port of a
Network Access Server (NAS) starts a Diameter NAS message exchange.
Information about the call, the identity of the user, and the user's
authentication information are packaged into a Diameter AA-Request
(AAR) message and sent to a server.
<vspace blankLines="1"/>
The server processes the information and responds with a Diameter
AA-Answer (AAA) message that contains authorization information for
the NAS, or a failure code (Result-Code AVP). A value of
DIAMETER_MULTI_ROUND_AUTH indicates an additional authentication
exchange, and several AAR and AAA messages may be exchanged until the
transaction completes.
<vspace blankLines="1"/>
Depending on the vale of the Auth-Request-Type AVP, the Diameter protocol allows
authorization-only requests that contain no authentication
information from the client. This capability goes beyond the Call Check capabilities provided
by RADIUS (<xref target="RFC2865">Section 5.6 of</xref>)
in that no access decision is requested. As a result, service cannot be started as a result of a
response to an authorization-only request without introducing a significant security vulnerability.
</t>
<section title="Diameter Session Establishment">
<t>
When the authentication or authorization exchange completes
successfully, the NAS application SHOULD start a session context. If
the Result-Code of DIAMETER_MULTI_ROUND_AUTH is returned, the
exchange continues until a success or error is returned.
<vspace blankLines="1"/>
If accounting is active, the application MUST also send an Accounting
message <xref target="I-D.ietf-dime-rfc3588bis"/>.
An Accounting-Record-Type of START_RECORD is sent
for a new session. If a session fails to start, the EVENT_RECORD
message is sent with the reason for the failure described.
<vspace blankLines="1"/>
Note that the return of an unsupportable Accounting-Realtime-Required
value <xref target="I-D.ietf-dime-rfc3588bis"/>
would result in a failure to establish the session.
</t>
</section>
<section title="Diameter Session Reauthentication or Reauthorization">
<t>
The Diameter Base protocol allows users to be periodically
reauthenticated and/or reauthorized. In such instances, the
Session-Id AVP in the AAR message MUST be the same as the one present
in the original authentication/authorization message.
<vspace blankLines="1"/>
A Diameter server informs the NAS of the maximum time allowed before
reauthentication or reauthorization via the
Authorization-Lifetime AVP <xref target="I-D.ietf-dime-rfc3588bis"/>.
A NAS MAY reauthenticate and/or reauthorize before the end, but A NAS MUST reauthenticate
and/or reauthorize at the end of
the period provided by the Authorization-Lifetime AVP. The failure
of a reauthentication exchange will terminate the service.
<vspace blankLines="1"/>
Furthermore, it is possible for Diameter servers to issue an
unsolicited reauthentication and/or reauthorization request (e.g.,
Re-Auth-Request (RAR) message <xref target="I-D.ietf-dime-rfc3588bis"/>)
to the NAS. Upon receipt of
such a message, the NAS MUST respond to the request with a Re-Auth-Answer (RAA)
message <xref target="I-D.ietf-dime-rfc3588bis"/>.
<vspace blankLines="1"/>
If the RAR properly identifies an active session, the NAS will
initiate a new local reauthentication or authorization sequence as
indicated by the Re-Auth-Request-Type value. This will cause the NAS
to send a new AAR message using the existing Session-Id. The server
will respond with an AAA message to specify the new service parameters.
<vspace blankLines="1"/>
If accounting is active, every change of authentication or
authorization SHOULD generate an accounting message. If the NAS
service is a continuation of the prior user context, then an
Accounting-Record-Type of INTERIM_RECORD indicating the new session
attributes and cumulative status would be appropriate. If a new user
or a significant change in authorization is detected by the NAS, then
the service may send two messages of the types STOP_RECORD and
START_RECORD. Accounting may change the subsession identifiers
(Acct-Session-ID, or Acct-Sub-Session-Id) to indicate such sub-sessions.
A service may also use a different Session-Id value for
accounting <xref target="I-D.ietf-dime-rfc3588bis">see Section 9.6 of</xref>.
<vspace blankLines="1"/>
However, the Diameter Session-ID AVP value used for the initial
authorization exchange MUST be used to generate an STR message when
the session context is terminated.
</t>
</section>
<section title="Diameter Session Termination">
<t>
When a NAS receives an indication that a user's session is being
disconnected by the client (e.g., LCP Terminate is received) or an
administrative command, the NAS MUST issue a
Session-Termination-Request (STR) <xref target="I-D.ietf-dime-rfc3588bis"/>
to its Diameter Server. This will ensure that
any resources maintained on the servers are freed appropriately.
<vspace blankLines="1"/>
Furthermore, a NAS that receives an Abort-Session-Request (ASR) <xref target="I-D.ietf-dime-rfc3588bis"/>
MUST issue an ASA if the session identified is active and
disconnect the PPP (or tunneling) session.
<vspace blankLines="1"/>
If accounting is active, an Accounting STOP_RECORD message <xref target="I-D.ietf-dime-rfc3588bis"/>
MUST be sent upon termination of the session context.
<vspace blankLines="1"/>
More information on Diameter Session Termination can be found in
<xref target="I-D.ietf-dime-rfc3588bis">Sections 8.4 and 8.5 of</xref>.
</t>
</section>
</section>
<section title="Diameter NAS Application Messages">
<t>
This section defines the Diameter message Command-Code
<xref target="I-D.ietf-dime-rfc3588bis"/>
values that MUST be supported by all Diameter implementations conforming to
this specification. The Command Codes are as follows:
</t>
<texttable align="center">
<ttcol align="left" width="60%">Command Name</ttcol>
<ttcol align="center">Abbrev.</ttcol>
<ttcol align="center">Code</ttcol>
<ttcol align="left">Reference</ttcol>
<c>AA-Request</c>
<c>AAR</c>
<c>265</c>
<c><xref target="AAR"/></c>
<c>AA-Answer</c>
<c>AAA</c>
<c>265</c>
<c><xref target="AAA"/></c>
<c>Re-Auth-Request</c>
<c>RAR</c>
<c>258</c>
<c><xref target="RAR"/></c>
<c>Re-Auth-Answer</c>
<c>RAA</c>
<c>258</c>
<c><xref target="RAA"/></c>
<c>Session-Termination-Request</c>
<c>STR</c>
<c>275</c>
<c><xref target="STR"/></c>
<c>Session-Termination-Answer</c>
<c>STA</c>
<c>275</c>
<c><xref target="STA"/></c>
<c>Abort-Session-Request</c>
<c>ASR</c>
<c>274</c>
<c><xref target="ASR"/></c>
<c>Abort-Session-Answer</c>
<c>ASA</c>
<c>274</c>
<c><xref target="ASA"/></c>
<c>Accounting-Request</c>
<c>ACR</c>
<c>271</c>
<c><xref target="ACR"/></c>
<c>Accounting-Answer</c>
<c>ACA</c>
<c>271</c>
<c><xref target="ACA"/></c>
</texttable>
<section title="AA-Request (AAR) Command" anchor="AAR">
<t>
The AA-Request (AAR), which is indicated by setting the Command-Code
field to 265 and the 'R' bit in the Command Flags field, is used to
request authentication and/or authorization for a given NAS user.
The type of request is identified through the Auth-Request-Type AVP <xref target="I-D.ietf-dime-rfc3588bis"/>
The recommended value for most RADIUS interoperability
situations is AUTHORIZE_AUTHENTICATE.
<vspace blankLines="1"/>
If Authentication is requested, the User-Name attribute SHOULD be
present, as well as any additional authentication AVPs that would
carry the password information. A request for authorization SHOULD
only include the information from which the authorization will be
performed, such as the User-Name, Called-Station-Id, or Calling-Station-Id AVPs.
All requests SHOULD contain AVPs uniquely
identifying the source of the call, such as Origin-Host and NAS-Port.
Certain networks MAY use different AVPs for authorization purposes.
A request for authorization will include some AVPs defined in <xref target="AUTHZ-AVP"/>.
<vspace blankLines="1"/>
It is possible for a single session to be authorized first and then
for an authentication request to follow.
<vspace blankLines="1"/>
This AA-Request message MAY be the result of a multi-round
authentication exchange, which occurs when the AA-Answer message is
received with the Result-Code AVP set to DIAMETER_MULTI_ROUND_AUTH.
A subsequent AAR message SHOULD be sent, with the User-Password AVP
that includes the user's response to the prompt, and MUST include any
State AVPs that were present in the AAA message.
<figure align="left" suppress-title="true" anchor="figAAR"><artwork><![CDATA[
Message Format
<AA-Request> ::= < Diameter Header: 265, REQ, PXY >
< Session-Id >
{ Auth-Application-Id }
{ Origin-Host }
{ Origin-Realm }
{ Destination-Realm }
{ Auth-Request-Type }
[ Destination-Host ]
[ NAS-Identifier ]
[ NAS-IP-Address ]
[ NAS-IPv6-Address ]
[ NAS-Port ]
[ NAS-Port-Id ]
[ NAS-Port-Type ]
[ Origin-AAA-Protocol ]
[ Origin-State-Id ]
[ Port-Limit ]
[ User-Name ]
[ User-Password ]
[ Service-Type ]
[ State ]
[ Authorization-Lifetime ]
[ Auth-Grace-Period ]
[ Auth-Session-State ]
[ Callback-Number ]
[ Called-Station-Id ]
[ Calling-Station-Id ]
[ Originating-Line-Info ]
[ Connect-Info ]
[ CHAP-Auth ]
[ CHAP-Challenge ]
* [ Framed-Compression ]
[ Framed-Interface-Id ]
[ Framed-IP-Address ]
* [ Framed-IPv6-Prefix ]
[ Framed-IP-Netmask ]
[ Framed-MTU ]
[ Framed-Protocol ]
[ ARAP-Password ]
[ ARAP-Security ]
* [ ARAP-Security-Data ]
* [ Login-IP-Host ]
* [ Login-IPv6-Host ]
[ Login-LAT-Group ]
[ Login-LAT-Node ]
[ Login-LAT-Port ]
[ Login-LAT-Service ]
* [ Tunneling ]
* [ Proxy-Info ]
* [ Route-Record ]
* [ AVP ]
]]></artwork></figure>
</t>
</section>
<section title="AA-Answer (AAA) Command" anchor="AAA">
<t>
The AA-Answer (AAA) message is indicated by setting the Command-Code
field to 265 and clearing the 'R' bit in the Command Flags field. It
is sent in response to the AA-Request (AAR) message. If
authorization was requested, a successful response will include the
authorization AVPs appropriate for the service being provided, as
defined in <xref target="AUTHZ-AVP"/>.
<vspace blankLines="1"/>
For authentication exchanges requiring more than a single round trip,
the server MUST set the Result-Code AVP to DIAMETER_MULTI_ROUND_AUTH.
An AAA message with this result code MAY include one Reply-Message or
more and MAY include zero or one State AVPs.
<vspace blankLines="1"/>
If the Reply-Message AVP was present, the network access server
SHOULD send the text to the user's client to display to the user,
instructing the client to prompt the user for a response. For
example, this capability can be achieved in PPP via PAP. If the
access client is unable to prompt the user for a new response, it
MUST treat the AA-Answer (AAA) with the Reply-Message AVP as an error and deny access.
<figure align="left" anchor="figAAA" suppress-title="true"><artwork><![CDATA[
Message Format
<AA-Answer> ::= < Diameter Header: 265, PXY >
< Session-Id >
{ Auth-Application-Id }
{ Auth-Request-Type }
{ Result-Code }
{ Origin-Host }
{ Origin-Realm }
[ User-Name ]
[ Service-Type ]
* [ Class ]
* [ Configuration-Token ]
[ Acct-Interim-Interval ]
[ Error-Message ]
[ Error-Reporting-Host ]
* [ Failed-AVP ]
[ Idle-Timeout ]
[ Authorization-Lifetime ]
[ Auth-Grace-Period ]
[ Auth-Session-State ]
[ Re-Auth-Request-Type ]
[ Multi-Round-Time-Out ]
[ Session-Timeout ]
[ State ]
* [ Reply-Message ]
[ Origin-AAA-Protocol ]
[ Origin-State-Id ]
* [ Filter-Id ]
[ Password-Retry ]
[ Port-Limit ]
[ Prompt ]
[ ARAP-Challenge-Response ]
[ ARAP-Features ]
[ ARAP-Security ]
* [ ARAP-Security-Data ]
[ ARAP-Zone-Access ]
[ Callback-Id ]
[ Callback-Number ]
[ Framed-Appletalk-Link ]
* [ Framed-Appletalk-Network ]
[ Framed-Appletalk-Zone ]
* [ Framed-Compression ]
[ Framed-Interface-Id ]
[ Framed-IP-Address ]
* [ Framed-IPv6-Prefix ]
[ Framed-IPv6-Pool ]
* [ Framed-IPv6-Route ]
[ Framed-IP-Netmask ]
* [ Framed-Route ]
[ Framed-Pool ]
[ Framed-IPX-Network ]
[ Framed-MTU ]
[ Framed-Protocol ]
[ Framed-Routing ]
* [ Login-IP-Host ]
* [ Login-IPv6-Host ]
[ Login-LAT-Group ]
[ Login-LAT-Node ]
[ Login-LAT-Port ]
[ Login-LAT-Service ]
[ Login-Service ]
[ Login-TCP-Port ]
* [ NAS-Filter-Rule ]
* [ QoS-Filter-Rule ]
* [ Tunneling ]
* [ Redirect-Host ]
[ Redirect-Host-Usage ]
[ Redirect-Max-Cache-Time ]
* [ Proxy-Info ]
* [ AVP ]
]]></artwork></figure>
</t>
</section>
<section title="Re-Auth-Request (RAR) Command" anchor="RAR">
<t>
A Diameter server may initiate a re-authentication and/or re-
authorization service for a particular session by issuing a Re-Auth-Request (RAR)
message <xref target="I-D.ietf-dime-rfc3588bis"/>.
<vspace blankLines="1"/>
For example, for pre-paid services, the Diameter server that
originally authorized a session may need some confirmation that the
user is still using the services.
<vspace blankLines="1"/>
If a NAS receives an RAR message with Session-Id equal to a currently
active session and a Re-Auth-Type that includes authentication, it
MUST initiate a re-authentication toward the user, if the service
supports this particular feature.
<figure align="left" anchor="figRAR" suppress-title="true"><artwork><![CDATA[
Message Format
<RA-Request> ::= < Diameter Header: 258, REQ, PXY >
< Session-Id >
{ Origin-Host }
{ Origin-Realm }
{ Destination-Realm }
{ Destination-Host }
{ Auth-Application-Id }
{ Re-Auth-Request-Type }
[ User-Name ]
[ Origin-AAA-Protocol ]
[ Origin-State-Id ]
[ NAS-Identifier ]
[ NAS-IP-Address ]
[ NAS-IPv6-Address ]
[ NAS-Port ]
[ NAS-Port-Id ]
[ NAS-Port-Type ]
[ Service-Type ]
[ Framed-IP-Address ]
[ Framed-IPv6-Prefix ]
[ Framed-Interface-Id ]
[ Called-Station-Id ]
[ Calling-Station-Id ]
[ Originating-Line-Info ]
[ Acct-Session-Id ]
[ Acct-Multi-Session-Id ]
[ State ]
* [ Class ]
[ Reply-Message ]
* [ Proxy-Info ]
* [ Route-Record ]
* [ AVP ]
]]></artwork></figure>
</t>
</section>
<section title="Re-Auth-Answer (RAA) Command" anchor="RAA">
<t>
The Re-Auth-Answer (RAA) message <xref target="I-D.ietf-dime-rfc3588bis"/>
is sent in response to the RAR. The Result-Code AVP MUST be present and indicates the
disposition of the request.
<vspace blankLines="1"/>
A successful RAA transaction MUST be followed by an AAR message.
<figure align="left" anchor="figRAA" suppress-title="true"><artwork><![CDATA[
Message Format
<RA-Answer> ::= < Diameter Header: 258, PXY >
< Session-Id >
{ Result-Code }
{ Origin-Host }
{ Origin-Realm }
[ User-Name ]
[ Origin-AAA-Protocol ]
[ Origin-State-Id ]
[ Error-Message ]
[ Error-Reporting-Host ]
* [ Failed-AVP ]
* [ Redirected-Host ]
[ Redirected-Host-Usage ]
[ Redirected-Host-Cache-Time ]
[ Service-Type ]
* [ Configuration-Token ]
[ Idle-Timeout ]
[ Authorization-Lifetime ]
[ Auth-Grace-Period ]
[ Re-Auth-Request-Type ]
[ State ]
* [ Class ]
* [ Reply-Message ]
[ Prompt ]
* [ Proxy-Info ]
* [ AVP ]
]]></artwork></figure>
</t>
</section>
<section title="Session-Termination-Request (STR) Command" anchor="STR">
<t>
The Session-Termination-Request (STR) message <xref target="I-D.ietf-dime-rfc3588bis"/>
is sent by the NAS to inform the Diameter Server that an authenticated and/or
authorized session is being terminated.
<figure align="left" anchor="figSTR" suppress-title="true"><artwork><![CDATA[
Message Format
<ST-Request> ::= < Diameter Header: 275, REQ, PXY >
< Session-Id >
{ Origin-Host }
{ Origin-Realm }
{ Destination-Realm }
{ Auth-Application-Id }
{ Termination-Cause }
[ User-Name ]
[ Destination-Host ]
* [ Class ]
[ Origin-AAA-Protocol ]
[ Origin-State-Id ]
* [ Proxy-Info ]
* [ Route-Record ]
* [ AVP ]
]]></artwork></figure>
</t>
</section>
<section title="Session-Termination-Answer (STA) Command" anchor="STA">
<t>
The Session-Termination-Answer (STA) message <xref target="I-D.ietf-dime-rfc3588bis"/>
is sent by the Diameter Server to acknowledge the notification that the session has
been terminated. The Result-Code AVP MUST be present and MAY contain
an indication that an error occurred while the STR was being serviced.
<vspace blankLines="1"/>
Upon sending or receiving the STA, the Diameter Server MUST release
all resources for the session indicated by the Session-Id AVP. Any
intermediate server in the Proxy-Chain MAY also release any
resources, if necessary.
<figure align="left" anchor="figSTA" suppress-title="true"><artwork><![CDATA[
Message Format
<ST-Answer> ::= < Diameter Header: 275, PXY >
< Session-Id >
{ Result-Code }
{ Origin-Host }
{ Origin-Realm }
[ User-Name ]
* [ Class ]
[ Error-Message ]
[ Error-Reporting-Host ]
* [ Failed-AVP ]
[ Origin-AAA-Protocol ]
[ Origin-State-Id ]
* [ Redirect-Host ]
[ Redirect-Host-Usase ]
[ Redirect-Max-Cache-Time ]
* [ Proxy-Info ]
* [ AVP ]
]]></artwork></figure>
</t>
</section>
<section title="Abort-Session-Request (ASR) Command" anchor="ASR">
<t>
The Abort-Session-Request (ASR) message <xref target="I-D.ietf-dime-rfc3588bis"/>
may be sent by any
server to the NAS providing session service, to request that the
session identified by the Session-Id be stopped.
<figure align="left" anchor="figASR" suppress-title="true"><artwork><![CDATA[
Message Format
<AS-Request> ::= < Diameter Header: 274, REQ, PXY >
< Session-Id >
{ Origin-Host }
{ Origin-Realm }
{ Destination-Realm }
{ Destination-Host }
{ Auth-Application-Id }
[ User-Name ]
[ Origin-AAA-Protocol ]
[ Origin-State-Id ]
[ NAS-Identifier ]
[ NAS-IP-Address ]
[ NAS-IPv6-Address ]
[ NAS-Port ]
[ NAS-Port-Id ]
[ NAS-Port-Type ]
[ Service-Type ]
[ Framed-IP-Address ]
[ Framed-IPv6-Prefix ]
[ Framed-Interface-Id ]
[ Called-Station-Id ]
[ Calling-Station-Id ]
[ Originating-Line-Info ]
[ Acct-Session-Id ]
[ Acct-Multi-Session-Id ]
[ State ]
* [ Class ]
* [ Reply-Message ]
* [ Proxy-Info ]
* [ Route-Record ]
* [ AVP ]
]]></artwork></figure>
</t>
</section>
<section title="Abort-Session-Answer (ASA) Command" anchor="ASA">
<t>
The ASA message <xref target="I-D.ietf-dime-rfc3588bis"/>
is sent in response to the ASR. The Result-Code
AVP MUST be present and indicates the disposition of the request.
<vspace blankLines="1"/>
If the session identified by Session-Id in the ASR was successfully
terminated, Result-Code is set to DIAMETER_SUCCESS. If the session
is not currently active, the Result-Code AVP is set to
DIAMETER_UNKNOWN_SESSION_ID. If the access device does not stop the
session for any other reason, the Result-Code AVP is set to
DIAMETER_UNABLE_TO_COMPLY.
<figure align="left" anchor="figASA" suppress-title="true"><artwork><![CDATA[
Message Format
<AS-Answer> ::= < Diameter Header: 274, PXY >
< Session-Id >
{ Result-Code }
{ Origin-Host }
{ Origin-Realm }
[ User-Name ]
[ Origin-AAA-Protocol ]
[ Origin-State-Id ]
[ State]
[ Error-Message ]
[ Error-Reporting-Host ]
* [ Failed-AVP ]
* [ Redirected-Host ]
[ Redirected-Host-Usage ]
[ Redirected-Max-Cache-Time ]
* [ Proxy-Info ]
* [ AVP ]
]]></artwork></figure>
</t>
</section>
<section title="Accounting-Request (ACR) Command" anchor="ACR">
<t>
The ACR message <xref target="I-D.ietf-dime-rfc3588bis"/>
is sent by the NAS to report its session
information to a target server downstream.
<vspace blankLines="1"/>
Either the Acct-Application-Id AVP or the Vendor-Specific-Application-Id AVP
MUST be present. If the Vendor-Specific-Application-Id grouped AVP
is present, it must have an Acct-Application-Id inside.
<vspace blankLines="1"/>
The AVPs listed in the Base protocol specification <xref target="I-D.ietf-dime-rfc3588bis"/>
MUST be assumed to be present, as
appropriate.
NAS service-specific accounting AVPs SHOULD be present
as described in <xref target="ACCT-AVP"/>
and the rest of this specification.
<figure align="left" anchor="figACR" suppress-title="true"><artwork><![CDATA[
Message Format
<AC-Request> ::= < Diameter Header: 271, REQ, PXY >
< Session-Id >
{ Origin-Host }
{ Origin-Realm }
{ Destination-Realm }
{ Accounting-Record-Type }
{ Accounting-Record-Number }
[ Acct-Application-Id ]
[ Vendor-Specific-Application-Id ]
[ User-Name ]
[ Accounting-Sub-Session-Id ]
[ Acct-Session-Id ]
[ Acct-Multi-Session-Id ]
[ Origin-AAA-Protocol ]
[ Origin-State-Id ]
[ Destination-Host ]
[ Event-Timestamp ]
[ Acct-Delay-Time ]
[ NAS-Identifier ]
[ NAS-IP-Address ]
[ NAS-IPv6-Address ]
[ NAS-Port ]
[ NAS-Port-Id ]
[ NAS-Port-Type ]
* [ Class ]
[ Service-Type ]
[ Termination-Cause ]
[ Accounting-Input-Octets ]
[ Accounting-Input-Packets ]
[ Accounting-Output-Octets ]
[ Accounting-Output-Packets ]
[ Acct-Authentic ]
[ Accounting-Auth-Method ]
[ Acct-Link-Count ]
[ Acct-Session-Time ]
[ Acct-Tunnel-Connection ]
[ Acct-Tunnel-Packets-Lost ]
[ Callback-Id ]
[ Callback-Number ]
[ Called-Station-Id ]
[ Calling-Station-Id ]
* [ Connection-Info ]
[ Originating-Line-Info ]
[ Authorization-Lifetime ]
[ Session-Timeout ]
[ Idle-Timeout ]
[ Port-Limit ]
[ Accounting-Realtime-Required ]
[ Acct-Interim-Interval ]
* [ Filter-Id ]
* [ NAS-Filter-Rule ]
* [ Qos-Filter-Rule ]
[ Framed-AppleTalk-Link ]
[ Framed-AppleTalk-Network ]
[ Framed-AppleTalk-Zone ]
[ Framed-Compression ]
[ Framed-Interface-Id ]
[ Framed-IP-Address ]
[ Framed-IP-Netmask ]
* [ Framed-IPv6-Prefix ]
[ Framed-IPv6-Pool ]
* [ Framed-IPv6-Route ]
[ Framed-IPX-Network ]
[ Framed-MTU ]
[ Framed-Pool ]
[ Framed-Protocol ]
* [ Framed-Route ]
[ Framed-Routing ]
* [ Login-IP-Host ]
* [ Login-IPv6-Host ]
[ Login-LAT-Group ]
[ Login-LAT-Node ]
[ Login-LAT-Port ]
[ Login-LAT-Service ]
[ Login-Service ]
[ Login-TCP-Port ]
* [ Tunneling ]
* [ Proxy-Info ]
* [ Route-Record ]
* [ AVP ]
]]></artwork></figure>
</t>
</section>
<section title="Accounting-Answer (ACA) Command" anchor="ACA">
<t>
The ACA message <xref target="I-D.ietf-dime-rfc3588bis"/>
is used to acknowledge an Accounting-Request command.
The Accounting-Answer command contains the same Session-Id
as the Request. If the Accounting-Request was protected by end-to-end security, then the
corresponding ACA message MUST be protected as well.
<vspace blankLines="1"/>
Only the target Diameter Server or home Diameter Server SHOULD
respond with the Accounting-Answer command.
<vspace blankLines="1"/>
Either the Acct-Application-Id AVP or the Vendor-Specific-Application-Id AVP
MUST be present, as it was in the request.
<vspace blankLines="1"/>
The AVPs listed in the Base protocol specification <xref target="I-D.ietf-dime-rfc3588bis"/>
MUST be assumed to be present, as
appropriate. NAS service-specific accounting AVPs SHOULD be present
as described in <xref target="ACCT-AVP"/>
and the rest of this specification.
<figure align="left" anchor="figACA" suppress-title="true"><artwork><![CDATA[
Message Format
<AC-Answer> ::= < Diameter Header: 271, PXY >
< Session-Id >
{ Result-Code }
{ Origin-Host }
{ Origin-Realm }
{ Accounting-Record-Type }
{ Accounting-Record-Number }
[ Acct-Application-Id ]
[ Vendor-Specific-Application-Id ]
[ User-Name ]
[ Accounting-Sub-Session-Id ]
[ Acct-Session-Id ]
[ Acct-Multi-Session-Id ]
[ Event-Timestamp ]
[ Error-Message ]
[ Error-Reporting-Host ]
* [ Failed-AVP ]
[ Origin-AAA-Protocol ]
[ Origin-State-Id ]
[ NAS-Identifier ]
[ NAS-IP-Address ]
[ NAS-IPv6-Address ]
[ NAS-Port ]
[ NAS-Port-Id ]
[ NAS-Port-Type ]
[ Service-Type ]
[ Termination-Cause ]
[ Accounting-Realtime-Required ]
[ Acct-Interim-Interval ]
* [ Class ]
* [ Proxy-Info ]
* [ Route-Record ]
* [ AVP ]
]]></artwork></figure>
</t>
</section>
</section>
<section title="Diameter NAS Application AVPs" anchor="D-N-A-AVPs">
<t>
The following sections define a new derived AVP data format, a set of application-specific AVPs and
describe the use of AVPs defined in other documents by the Diameter NAS Application.
</t>
<section title="Derived AVP Data Formats" anchor="D-A-D-F">
<section title="QoSFilterRule" anchor="QFR-Format">
<t>
The QosFilterRule format is derived from the OctetString AVP Base
Format. It uses the ASCII charset. Packets may be marked or
metered based on the following information:
<list style="symbols">
<t>Direction (in or out)</t>
<t>Source and destination IP address (possibly masked)</t>
<t>Protocol</t>
<t>Source and destination port (lists or ranges)</t>
<t>DSCP values (no mask or range)</t>
</list>
Rules for the appropriate direction are evaluated in order; the
first matched rule terminates the evaluation. Each packet is
evaluated once. If no rule matches, the packet is treated as best
effort. An access device unable to interpret or apply a QoS rule
SHOULD NOT terminate the session.
<vspace blankLines="1"/>
QoSFilterRule filters MUST follow the following format:
<vspace blankLines="1"/>
<?rfc subcompact="true"?>
<list>
<t>action dir proto from src to dst [options]</t>
<t>where
<vspace blankLines="1"/>
<list style="hanging" hangIndent="12">
<t hangText="action">
<list style="hanging">
<t hangText="tag">
Mark packet with a specific DSCP <xref target="RFC2474"/>
</t>
<t hangText="meter">Meter traffic</t>
</list>
<vspace blankLines="1"/>
</t>
<t hangText="dir">
The format is as described under IPFilterRule
<xref target="I-D.ietf-dime-rfc3588bis"/>
<vspace blankLines="1"/>
</t>
<t hangText="proto">
The format is as described under IPFilterRule
<xref target="I-D.ietf-dime-rfc3588bis"/>
<vspace blankLines="1"/>
</t>
<t hangText="src and dst">
The format is as described under IPFilterRule
<xref target="I-D.ietf-dime-rfc3588bis"/>
<vspace blankLines="1"/>
</t>
</list>
</t>
</list>
<?rfc subcompact="false"?>
The options are described in <xref target="Q-F-R-AVP"/>.
<vspace blankLines="1"/>
The rule syntax is a modified subset of ipfw(8) from FreeBSD,
and the ipfw.c code may provide a useful base for implementations.
</t>
</section>
</section>
<section title="NAS Session AVPs" anchor="SESSION-AVP">
<t>
Diameter reserves the AVP Codes 0 - 255 for RADIUS functions that are
implemented in Diameter.
<vspace blankLines="1"/>
AVPs new to Diameter have code values of 256 and greater. A Diameter
message that includes one of these AVPs may represent functions not
present in the RADIUS environment and may cause interoperability
issues, should the request traverse an AAA system that only supports
the RADIUS protocol.
</t>
<section title="Call and Session Information">
<t>
This section describes the AVPs specific to NAS Diameter applications
that are needed to identify the call and session context and status
information. On a request, this information allows the server to qualify the session.
<vspace blankLines="1"/>
These AVPs are used in addition to the following
AVPs from the base protocol specification <xref target="I-D.ietf-dime-rfc3588bis"/>:
<vspace blankLines="1"/>
<?rfc subcompact="yes"?>
<list>
<t>Session-Id</t>
<t>Auth-Application-Id</t>
<t>Origin-Host</t>
<t>Origin-Realm</t>
<t>Auth-Request-Type</t>
<t>Termination-Cause</t>
</list>
<?rfc subcompact="no"?>
<vspace blankLines="1"/>
The following table gives the possible flag values for the session level AVPs
and specifies whether the AVP MAY be encrypted.
<figure align="left" suppress-title="true"><artwork><![CDATA[
+---------------------+
| AVP Flag rules |
|----+-----+----+-----|----+
| | |SHLD| MUST| |
Attribute Name Section Defined |MUST| MAY | NOT| NOT|Encr|
-----------------------------------------|----+-----+----+-----|----|
NAS-Port 4.2.2 | M | P | | V | Y |
NAS-Port-Id 4.2.3 | M | P | | V | Y |
NAS-Port-Type 4.2.4 | M | P | | V | Y |
Called-Station-Id 4.2.5 | M | P | | V | Y |
Calling-Station-Id 4.2.6 | M | P | | V | Y |
Connect-Info 4.2.7 | M | P | | V | Y |
Originating-Line-Info 4.2.8 | | M,P | | V | Y |
Reply-Message 4.2.9 | M | P | | V | Y |
-----------------------------------------|----+-----+----+-----|----|
]]></artwork></figure>
</t>
</section>
<section title="NAS-Port AVP" anchor="N-P">
<t>
The NAS-Port AVP (AVP Code 5) is of type Unsigned32 and contains the
physical or virtual port number of the NAS which is authenticating
the user. Note that "port" is meant in its sense as a service
connection on the NAS, not as an IP protocol identifier.
<vspace blankLines="1"/>
Either the NAS-Port AVP or the NAS-Port-Id AVP (<xref target="N-P-I"/>)
SHOULD be present in
the AA-Request (AAR, <xref target="AAR"/>)
command if the NAS differentiates among its ports.
</t>
</section>
<section title="NAS-Port-Id AVP" anchor="N-P-I">
<t>
The NAS-Port-Id AVP (AVP Code 87) is of type UTF8String and consists
of ASCII text identifying the port of the NAS authenticating the
user. Note that "port" is meant in its sense as a service connection
on the NAS, not as an IP protocol identifier.
<vspace blankLines="1"/>
Either the NAS-Port-Id or the NAS-Port (<xref target="N-P"/>)
SHOULD be present in the AA-Request (AAR, <xref target="AAR"/>)
command if the NAS differentiates among its ports.
NAS-Port-Id is intended for use by NASes that cannot conveniently number their ports.
</t>
</section>
<section title="NAS-Port-Type AVP">
<t>
The NAS-Port-Type AVP (AVP Code 61) is of type Enumerated and
contains the type of the port on which the NAS is authenticating the
user. This AVP SHOULD be present if the NAS uses the same NAS-Port
number ranges for different service types concurrently.
<vspace blankLines="1"/>
The currently supported values of the NAS-Port-Type AVP
are listed in <xref target="RADIUSTypes"/>.
</t>
</section>
<section title="Called-Station-Id AVP">
<t>
The Called-Station-Id AVP (AVP Code 30) is of type UTF8String and
allows the NAS to send the ASCII string describing the Layer 2
address the user contacted in the request. For dialup access, this
can be a phone number obtained by using the Dialed Number Identification Service
(DNIS) or a similar technology. Note that this may be different from
the phone number the call comes in on. For use with IEEE 802 access,
the Called-Station-Id MAY contain a MAC address formatted as
described in <xref target="RFC3580"/>.
It SHOULD only be present in authentication and/or authorization requests.
<vspace blankLines="1"/>
If the Called-Station-Id AVP is present in an AAR message,
Auth-Request-Type AVP is set to AUTHORIZE_ONLY and the
User-Name AVP is absent, the Diameter Server MAY perform
authorization based on this AVP. This can be used by a NAS to
request whether a call should be answered based on the DNIS.
<vspace blankLines="1"/>
The codification of this field's allowed usage range is outside the scope of this specification.
</t>
</section>
<section title="Calling-Station-Id AVP">
<t>
The Calling-Station-Id AVP (AVP Code 31) is of type UTF8String and
allows the NAS to send the ASCII string describing the Layer 2
address from which the user connected in the request. For dialup
access, this is the phone number the call came from, using Automatic
Number Identification (ANI) or a similar technology. For use with
IEEE 802 access, the Calling-Station-Id AVP MAY contain a MAC
address, formated as described in <xref target="RFC3580"/>.
It SHOULD only be present in authentication and/or authorization requests.
<vspace blankLines="1"/>
If the Calling-Station-Id AVP is present in an AAR message,
the Auth-Request-Type AVP is set to
AUTHORIZE_ONLY and the
User-Name AVP is absent, the Diameter Server MAY perform
authorization based on the value of this AVP. This can be used by a NAS to
request whether a call should be answered based on the Layer 2
address (ANI, MAC Address, etc.)
<vspace blankLines="1"/>
The codification of this field's allowed usage range is outside the scope of this specification.
</t>
</section>
<section title="Connect-Info AVP">
<t>
The Connect-Info AVP (AVP Code 77) is of type UTF8String and is sent
in the AA-Request message or an ACR message with the value of the
Accounting-Record-Type AVP set to STOP. When sent in the
AA-Request, it indicates the nature of the user's connection.
The connection speed SHOULD be included at the beginning of the first
Connect-Info AVP in the message. If the transmit and receive
connection speeds differ, both may be included in the first AVP with
the transmit speed listed first (the speed at which the NAS modem transmits),
then a slash (/), then the receive speed, and then other optional information.
<vspace blankLines="1"/>
For example: "28800 V42BIS/LAPM" or "52000/31200 V90"
<vspace blankLines="1"/>
If sent in an ACR message with the value of the
Accounting-Record-Type AVP set to STOP, this attribute may summarize statistics
relating to session quality. For example, in IEEE 802.11, the
Connect-Info AVP may contain information on the number of link
layer retransmissions. The exact format of this attribute is implementation specific.
</t>
</section>
<section title="Originating-Line-Info AVP">
<t>
The Originating-Line-Info AVP (AVP Code 94) is of type OctetString
and is sent by the NAS system to convey information about the origin
of the call from an SS7 system.
<vspace blankLines="1"/>
The originating line information (OLI) element indicates the nature
and/or characteristics of the line from which a call originated
(e.g., pay phone, hotel, cellular). Telephone companies are starting
to offer OLI to their customers as an option over Primary Rate
Interface (PRI). Internet Service Providers (ISPs) can use OLI in
addition to Called-Station-Id and Calling-Station-Id attributes to
differentiate customer calls and to define different services.
<vspace blankLines="1"/>
The Value field contains two octets (00 - 99). ANSI T1.113 and
BELLCORE 394 can be used for additional information about these
values and their use. For information on the currently assigned
values, see <xref target="ANITypes"/>.
</t>
</section>
<section title="Reply-Message AVP">
<t>
The Reply-Message AVP (AVP Code 18) is of type UTF8String and
contains text that MAY be displayed to the user. When used in an
AA-Answer message with a successful Result-Code AVP, it indicates
success. When found in an AAA message with a Result-Code other than
DIAMETER_SUCCESS, the AVP contains a failure message.
<vspace blankLines="1"/>
The Reply-Message AVP MAY contain text to prompt the user
before another AA-Request attempt. When used in an AA-Answer message containing a
Result-Code AVP with the value DIAMETER_MULTI_ROUND_AUTH or in an Re-Auth-Request
message, it MAY contain text to prompt the user for a response.
</t>
</section>
</section>
<section title="NAS Authentication AVPs">
<t>
This section defines the AVPs necessary to carry the authentication
information in the Diameter protocol. The functionality defined here
provides a RADIUS-like AAA service over a more reliable and secure
transport, as defined in the base protocol <xref target="I-D.ietf-dime-rfc3588bis"/>.
<vspace blankLines="1"/>
The following table gives the possible flag values for the session level AVPs
and specifies whether the AVP MAY be encrypted.
<figure align="left" suppress-title="true"><artwork><![CDATA[
+---------------------+
| AVP Flag rules |
|----+-----+----+-----|----+
| | |SHLD| MUST| |
Attribute Name Section Defined |MUST| MAY | NOT| NOT|Encr|
-----------------------------------------|----+-----+----+-----|----|
User-Password 4.3.1 | M | P | | V | Y |
Password-Retry 4.3.2 | M | P | | V | Y |
Prompt 4.3.3 | M | P | | V | Y |
CHAP-Auth 4.3.4 | M | P | | V | Y |
CHAP-Algorithm 4.3.5 | M | P | | V | Y |
CHAP-Ident 4.3.6 | M | P | | V | Y |
CHAP-Response 4.3.7 | M | P | | V | Y |
CHAP-Challenge 4.3.8 | M | P | | V | Y |
ARAP-Password 4.3.9 | M | P | | V | Y |
ARAP-Challenge-Response 4.3.10 | M | P | | V | Y |
ARAP-Security 4.3.11 | M | P | | V | Y |
ARAP-Security-Data 4.3.12 | M | P | | V | Y |
-----------------------------------------|----+-----+----+-----|----|
]]></artwork></figure>
</t>
<section title="User-Password AVP">
<t>
The User-Password AVP (AVP Code 2) is of type OctetString and
contains the password of the user to be authenticated, or the user's
input in a multi-round authentication exchange.
<vspace blankLines="1"/>
The User-Password AVP contains a user password or one-time password
and therefore represents sensitive information. As required in <xref target="I-D.ietf-dime-rfc3588bis"/>,
Diameter messages are encrypted by using IPsec or TLS.
Unless this AVP is used for one-time passwords, the User-Password AVP
SHOULD NOT be used in untrusted proxy environments without encrypting
it by using end-to-end security techniques.
<vspace blankLines="1"/>
The clear-text password (prior to encryption) MUST NOT be longer than 128 bytes in length.
</t>
</section>
<section title="Password-Retry AVP">
<t>
The Password-Retry AVP (AVP Code 75) is of type Unsigned32 and MAY be
included in the AA-Answer if the Result-Code indicates an
authentication failure. The value of this AVP indicates how many
authentication attempts a user is permitted before being
disconnected. This AVP is primarily intended for use when the
Framed-Protocol AVP (<xref target="F-P-AVP"/>)
is set to ARAP.
</t>
</section>
<section title="Prompt AVP">
<t>
The Prompt AVP (AVP Code 76) is of type Enumerated and MAY be present
in the AA-Answer message. When present, it is used by the NAS to
determine whether the user's response, when entered, should be echoed.
<vspace blankLines="1"/>
The supported values are listed in <xref target="RADIUSTypes"/>
</t>
</section>
<section title="CHAP-Auth AVP" anchor="C-AUTH-AVP">
<t>
The CHAP-Auth AVP (AVP Code 402) is of type Grouped and contains the
information necessary to authenticate a user using the PPP
Challenge-Handshake Authentication Protocol (CHAP) <xref target="RFC1994"/>.
If the CHAP-Auth AVP is found in a message,
the CHAP-Challenge AVP <xref target="C-C-AVP"/>
MUST be present as well. The optional AVPs containing the CHAP response
depend upon the value of the CHAP-Algorithm AVP <xref target="C-C-AVP"/>.
The grouped AVP has the following ABNF grammar:
<figure align="left" suppress-title="true"><artwork><![CDATA[
CHAP-Auth ::= < AVP Header: 402 >
{ CHAP-Algorithm }
{ CHAP-Ident }
[ CHAP-Response ]
* [ AVP ]
]]></artwork></figure>
</t>
</section>
<section title="CHAP-Algorithm AVP" anchor="C-A-AVP">
<t>
The CHAP-Algorithm AVP (AVP Code 403) is of type Enumerated and
contains the algorithm identifier used in the computation of the
CHAP response <xref target="RFC1994"/>.
The following values are currently supported:
<list style="hanging">
<t hangText="CHAP with MD5 5">
The CHAP response is computed by using the procedure described
in <xref target="RFC1994"/>
This algorithm requires that the CHAP-Response AVP <xref target="C-R-AVP"/>
MUST be present in the CHAP-Auth AVP <xref target="C-AUTH-AVP"/>.
</t>
</list>
</t>
</section>
<section title="CHAP-Ident AVP">
<t>
The CHAP-Ident AVP (AVP Code 404) is of type OctetString and contains
the 1 octet CHAP Identifier used in the computation of the CHAP
response <xref target="RFC1994"/>
</t>
</section>
<section title="CHAP-Response AVP" anchor="C-R-AVP">
<t>
The CHAP-Response AVP (AVP Code 405) is of type OctetString and
contains the 16 octet authentication data provided by the user in
response to the CHAP challenge <xref target="RFC1994"/>.
</t>
</section>
<section title="CHAP-Challenge AVP" anchor="C-C-AVP">
<t>
The CHAP-Challenge AVP (AVP Code 60) is of type OctetString and
contains the CHAP Challenge sent by the NAS to the CHAP peer
<xref target="RFC1994"/>.
</t>
</section>
<section title="ARAP-Password AVP">
<t>
The ARAP-Password AVP (AVP Code 70) is of type OctetString and is
only present when the Framed-Protocol AVP (<xref target="F-P-AVP"/>)
is included in the message and is set to ARAP. This AVP MUST NOT be
present if either the User-Password or the CHAP-Auth AVP is present.
See <xref target="RFC2869"/> for more information on the contents of this AVP.
</t>
</section>
<section title="ARAP-Challenge-Response AVP">
<t>
The ARAP-Challenge-Response AVP (AVP Code 84) is of type OctetString
and is only present when the Framed-Protocol AVP (<xref target="F-P-AVP"/>)
is included in the message and is set to ARAP. This AVP contains an
8 octet response to the dial-in client's challenge. The RADIUS
server calculates this value by taking the dial-in client's challenge
from the high-order 8 octets of the ARAP-Password AVP and performing
DES encryption on this value with the authenticating user's password
as the key. If the user's password is fewer than 8 octets in length,
the password is padded at the end with NULL octets to a length of 8before it is used as a key.
</t>
</section>
<section title="ARAP-Security AVP" anchor="A-S-AVP">
<t>
The ARAP-Security AVP (AVP Code 73) is of type Unsigned32 and MAY be
present in the AA-Answer message if the Framed-Protocol AVP (<xref target="F-P-AVP"/>) is
set to the value of ARAP, and the Result-Code AVP (<xref target="I-D.ietf-dime-rfc3588bis"/>, Section 7.1)
is set to DIAMETER_MULTI_ROUND_AUTH. See <xref target="RFC2869"/> for more
information on the contents of this AVP.
</t>
</section>
<section title="ARAP-Security-Data AVP">
<t>
The ARAP-Security-Data AVP (AVP Code 74) is of type OctetString and MAY be
present in the AA-Request or AA-Answer message if the Framed-Protocol
AVP (<xref target="F-P-AVP"/>)
is set to the value of ARAP and the Result-Code AVP (<xref target="I-D.ietf-dime-rfc3588bis"/>, Section 7.1)
is set to
DIAMETER_MULTI_ROUND_AUTH. This AVP contains the security module
challenge or response associated with the ARAP Security Module
specified in the ARAP-Security AVP (<xref target="A-S-AVP"/>).
</t>
</section>
</section>
<section title="NAS Authorization AVPs" anchor="AUTHZ-AVP">
<t>
This section contains the authorization AVPs supported in the NAS
Application. The Service-Type AVP SHOULD be present in all messages
and, based on its value, additional AVPs defined in this section and
<xref target="TUNNELING-AVPS"/>
MAY be present.
<vspace blankLines="1"/>
The following table gives the possible flag values for the session level AVPs
and specifies whether the AVP MAY be encrypted.
<figure align="left" suppress-title="true"><artwork><![CDATA[
+---------------------+
| AVP Flag rules |
|----+-----+----+-----|----+
| | |SHLD| MUST| |
Attribute Name Section Defined |MUST| MAY | NOT| NOT|Encr|
-----------------------------------------|----+-----+----+-----|----|
Service-Type 4.4.1 | M | P | | V | Y |
Callback-Number 4.4.2 | M | P | | V | Y |
Callback-Id 4.4.3 | M | P | | V | Y |
Idle-Timeout 4.4.4 | M | P | | V | Y |
Port-Limit 4.4.5 | M | P | | V | Y |
NAS-Filter-Rule 4.4.6 | M | P | | V | Y |
Filter-Id 4.4.7 | M | P | | V | Y |
Configuration-Token 4.4.8 | M | | | P,V | |
QoS-Filter-Rule 4.4.9 | | | | | |
Framed-Protocol 4.4.10.1 | M | P | | V | Y |
Framed-Routing 4.4.10.2 | M | P | | V | Y |
Framed-MTU 4.4.10.3 | M | P | | V | Y |
Framed-Compression 4.4.10.4 | M | P | | V | Y |
Framed-IP-Address 4.4.10.5.1 | M | P | | V | Y |
Framed-IP-Netmask 4.4.10.5.2 | M | P | | V | Y |
Framed-Route 4.4.10.5.3 | M | P | | V | Y |
Framed-Pool 4.4.10.5.4 | M | P | | V | Y |
Framed-Interface-Id 4.4.10.5.5 | M | P | | V | Y |
Framed-IPv6-Prefix 4.4.10.5.6 | M | P | | V | Y |
Framed-IPv6-Route 4.4.10.5.7 | M | P | | V | Y |
Framed-IPv6-Pool 4.4.10.5.8 | M | P | | V | Y |
Framed-IPX-Network 4.4.10.6.1 | M | P | | V | Y |
Framed-Appletalk-Link 4.4.10.7.1 | M | P | | V | Y |
Framed-Appletalk-Network 4.4.10.7.2 | M | P | | V | Y |
Framed-Appletalk-Zone 4.4.10.7.3 | M | P | | V | Y |
ARAP-Features 4.4.10.8.1 | M | P | | V | Y |
ARAP-Zone-Access 4.4.10.8.2 | M | P | | V | Y |
Login-IP-Host 4.4.11.1 | M | P | | V | Y |
Login-IPv6-Host 4.4.11.2 | M | P | | V | Y |
Login-Service 4.4.11.3 | M | P | | V | Y |
Login-TCP-Port 4.4.11.4.1 | M | P | | V | Y |
Login-LAT-Service 4.4.11.5.1 | M | P | | V | Y |
Login-LAT-Node 4.4.11.5.2 | M | P | | V | Y |
Login-LAT-Group 4.4.11.5.3 | M | P | | V | Y |
Login-LAT-Port 4.4.11.5.4 | M | P | | V | Y |
-----------------------------------------|----+-----+----+-----|----|
]]></artwork></figure>
</t>
<section title="Service-Type AVP" anchor="S-T-AVP">
<t>
The Service-Type AVP (AVP Code 6) is of type Enumerated and contains
the type of service the user has requested or the type of service to
be provided. One such AVP MAY be present in an authentication and/or
authorization request or response. A NAS is not required to
implement all of these service types. It MUST treat unknown or
unsupported Service-Types received in a response as a failure and end
the session with a DIAMETER_INVALID_AVP_VALUE Result-Code.
<vspace blankLines="1"/>
When used in a request, the Service-Type AVP SHOULD be considered a
hint to the server that the NAS believes the user would prefer the
kind of service indicated. The server is not required to honor the
hint. Furthermore, if the service specified by the server is
supported, but not compatible with the current mode of access, the
NAS MUST fail to start the session. The NAS MUST also generate the
appropriate error message(s).
<vspace blankLines="1"/>
The complete list of defined values that the Service-Type AVP can take
can be found in <xref target="RFC2865"/>
and <xref target="RADIUSTypes"/>, but the following values require further qualification here:
<vspace blankLines="1"/>
<?rfc subcompact="true"?>
<list>
<t>
<list style="hanging">
<t hangText="Login (1)">
<vspace blankLines="0"/>
The user should be connected to a host. The message MAY include additional AVPs
as defined in <xref target="TCP-S"/> or <xref target="LAT-S"/>.
<vspace blankLines="1"/>
</t>
<t hangText="Framed (2)">
<vspace blankLines="0"/>
A Framed Protocol, such as PPP or SLIP, should be started for the User.
The message MAY include additional AVPs defined in <xref target="F-A-A-AVP"/>,
or <xref target="TUNNELING-AVPS"/>
for tunneling services.
<vspace blankLines="1"/>
</t>
<t hangText="Callback Login (3)">
<vspace blankLines="0"/>
The user should be disconnected and called back, then connected
to a host. The message MAY include additional AVPs defined in this Section.
<vspace blankLines="1"/>
</t>
<t hangText="Callback Framed (4)">
<vspace blankLines="0"/>
The user should be disconnected and called back, and then a Framed
Protocol, such as PPP or SLIP, should be started for the User.
The message MAY include additional AVPs defined in <xref target="F-A-A-AVP"/>,
or <xref target="TUNNELING-AVPS"/>
for tunneling services.
</t>
</list>
</t>
</list>
<?rfc subcompact="false"?>
</t>
</section>
<section title="Callback-Number AVP" anchor="C-N-AVP">
<t>
The Callback-Number AVP (AVP Code 19) is of type UTF8String and
contains a dialing string to be used for callback. It MAY be used in
an authentication and/or authorization request as a hint to the
server that a Callback service is desired, but the server is not
required to honor the hint in the corresponding response.
<vspace blankLines="1"/>
The codification of this field's allowed usage range is outside the
scope of this specification.
</t>
</section>
<section title="Callback-Id AVP">
<t>
The Callback-Id AVP (AVP Code 20) is of type UTF8String and contains
the name of a place to be called, to be interpreted by the NAS. This
AVP MAY be present in an authentication and/or authorization
response.
<vspace blankLines="1"/>
This AVP is not roaming-friendly as it assumes that the Callback-Id
is configured on the NAS. Using the Callback-Number AVP <xref target="C-N-AVP"/>
is therefore preferable.
</t>
</section>
<section title="Idle-Timeout AVP">
<t>
The Idle-Timeout AVP (AVP Code 28) is of type Unsigned32 and sets the
maximum number of consecutive seconds of idle connection allowable to
the user before termination of the session or before a prompt is
issued. The default is none, or system specific.
</t>
</section>
<section title="Port-Limit AVP">
<t>
The Port-Limit AVP (AVP Code 62) is of type Unsigned32 and sets the
maximum number of ports the NAS provides to the user. It MAY be used
in an authentication and/or authorization request as a hint to the
server that multilink PPP <xref target="RFC1990"/>
service is desired, but the server
is not required to honor the hint in the corresponding response.
</t>
</section>
<section title="NAS-Filter-Rule AVP" anchor="N-F-R-AVP">
<t>
The NAS-Filter-Rule AVP (AVP Code 400) is of type IPFilterRule and
provides filter rules that need to be configured on the NAS for the
user. One or more of these AVPs MAY be present in an authorization
response.
</t>
</section>
<section title="Filter-Id AVP">
<t>
The Filter-Id AVP (AVP Code 11) is of type UTF8String and contains
the name of the filter list for this user. Zero or more Filter-Id
AVPs MAY be sent in an authorization answer.
<vspace blankLines="1"/>
Identifying a filter list by name allows the filter to be used on
different NASes without regard to filter-list implementation details.
However, this AVP is not roaming-friendly, as filter naming differs
from one service provider to another.
<vspace blankLines="1"/>
In environments where backward compatibility with RADIUS is not required,
it is RECOMMENDED that the
NAS-Filter-Rule AVP <xref target="N-F-R-AVP"/>
be used instead.
</t>
</section>
<section title="Configuration-Token AVP">
<t>
The Configuration-Token AVP (AVP Code 78) is of type OctetString and
is sent by a Diameter Server to a Diameter Proxy Agent or Translation
Agent in an AA-Answer command to indicate a type of user profile to
be used. It should not be sent to a Diameter Client (NAS).
<vspace blankLines="1"/>
The format of the Data field of this AVP is site specific.
</t>
</section>
<section title="QoS-Filter-Rule AVP" anchor="Q-F-R-AVP">
<t>
The QoS-Filter-Rule AVP (AVP Code 407) is of
type QoSFilterRule <xref target="QFR-Format"/>
and
provides QoS filter rules that need to be configured on the NAS for
the user. One or more such AVPs MAY be present in an authorization
response.
<vspace blankLines="1"/>
<list style="hanging" hangIndent="6">
<t hangText="DSCP <color>">
If action is set to tag <xref target="QFR-Format"/>
this option MUST be included in the rule.
<vspace blankLines="1"/>
Color values are defined in <xref target="RFC2474"/>.
Exact matching of DSCP values is required (no masks or
ranges).
</t>
<t hangText="metering <rate> <color_under> <color_over>">
The metering option provides Assured Forwarding, as defined in
<xref target="RFC2597"/>.
and MUST be present if the action is set to meter <xref target="QFR-Format"/>
The rate option is
the throughput, in bits per second, used by the access device to mark packets.
Traffic over the rate is marked with the color_over
codepoint, and traffic under the rate is marked with the color_under codepoint.
The color_under and color_over options contain the drop
preferences and MUST conform to the recommended
codepoint keywords described in <xref target="RFC2597"/>
(e.g., AF13).
<vspace blankLines="1"/>
The metering option also supports the strict limit on traffic required by Expedited
Forwarding, as defined in <xref target="RFC3246"/>.
The color_over option may contain the keyword "drop"
to prevent forwarding of traffic that exceeds the rate parameter.
</t>
</list>
</t>
</section>
<section title="Framed Access Authorization AVPs" anchor="F-A-A-AVP">
<t>
This section lists the authorization AVPs necessary to
support framed access, such as PPP and SLIP. AVPs defined in this
section MAY be present in a message if the Service-Type AVP was set
to "Framed" or "Callback Framed".
</t>
<section title="Framed-Protocol AVP" anchor="F-P-AVP">
<t>
The Framed-Protocol AVP (AVP Code 7) is of type Enumerated and
contains the framing to be used for framed access. This AVP MAY be
present in both requests and responses. The supported values are
listed in <xref target="RADIUSTypes"/>.
</t>
</section>
<section title="Framed-Routing AVP">
<t>
The Framed-Routing AVP (AVP Code 10) is of type Enumerated and
contains the routing method for the user when the user is a router to
a network. This AVP SHOULD only be present in authorization
responses. The supported values are listed in <xref target="RADIUSTypes"/>.
</t>
</section>
<section title="Framed-MTU AVP">
<t>
The Framed-MTU AVP (AVP Code 12) is of type Unsigned32 and contains
the Maximum Transmission Unit (MTU) to be configured for the user, when it
is not negotiated by some other means (such as PPP). This AVP SHOULD
only be present in authorization responses. The MTU value MUST be in
the range from 64 to 65535.
</t>
</section>
<section title="Framed-Compression AVP">
<t>
The Framed-Compression AVP (AVP Code 13) is of type Enumerated and
contains the compression protocol to be used for the link. It MAY be
used in an authorization request as a hint to the server that a
specific compression type is desired, but the server is not required
to honor the hint in the corresponding response.
<vspace blankLines="1"/>
More than one compression protocol AVP MAY be sent. The NAS is
responsible for applying the proper compression protocol to the
appropriate link traffic.
<vspace blankLines="1"/>
The supported values are listed in <xref target="RADIUSTypes"/>.
</t>
</section>
<section title="IP Access Authorization AVPs">
<t>
The AVPs defined in this section are used when the user requests, or
is being granted, access service to IP.
</t>
<section title="Framed-IP-Address AVP">
<t>
The Framed-IP-Address AVP (AVP Code 8) <xref target="RFC2865"/>
is of type OctetString and contains an IPv4 address of the type specified in the
attribute value to be configured for the user. It MAY be used in an
authorization request as a hint to the server that a specific address
is desired, but the server is not required to honor the hint in the corresponding response.
<vspace blankLines="1"/>
Two values have special significance: 0xFFFFFFFF and 0xFFFFFFFE. The
value 0xFFFFFFFF indicates that the NAS should allow the user to
select an address (i.e., negotiated). The value 0xFFFFFFFE indicates
that the NAS should select an address for the user (e.g., assigned
from a pool of addresses kept by the NAS).
</t>
</section>
<section title="Framed-IP-Netmask AVP">
<t>
The Framed-IP-Netmask AVP (AVP Code 9) is of type OctetString and
contains the four octets of the IPv4 netmask to be configured for the
user when the user is a router to a network. It MAY be used in an
authorization request as a hint to the server that a specific netmask
is desired, but the server is not required to honor the hint in the
corresponding response. This AVP MUST be present in a response if
the request included this AVP with a value of 0xFFFFFFFF.
</t>
</section>
<section title="Framed-Route AVP">
<t>
The Framed-Route AVP (AVP Code 22) is of type UTF8String and contains
the ASCII routing information to be configured for the user on the
NAS. Zero or more of these AVPs MAY be present in an authorization
response.
<vspace blankLines="1"/>
The string MUST contain a destination prefix in dotted quad form
optionally followed by a slash and a decimal length specifier stating
how many high-order bits of the prefix should be used. This is
followed by a space, a gateway address in dotted quad form, a space,
and one or more metrics separated by spaces; for example,
<list>
<t>"192.168.1.0/24 192.168.1.1 1"</t>
</list>
The length specifier may be omitted, in which case it should default
to 8 bits for class A prefixes, to 16 bits for class B prefixes, and
to 24 bits for class C prefixes; for example,
<list>
<t>"192.168.1.0 192.168.1.1 1"</t>
</list>
Whenever the gateway address is specified as "0.0.0.0" the IP address
of the user SHOULD be used as the gateway address.
</t>
</section>
<section title="Framed-Pool AVP">
<t>
The Framed-Pool AVP (AVP Code 88) is of type OctetString and contains
the name of an assigned address pool that SHOULD be used to assign an
address for the user. If a NAS does not support multiple address
pools, the NAS SHOULD ignore this AVP. Address pools are usually
used for IP addresses but can be used for other protocols if the NAS
supports pools for those protocols.
<vspace blankLines="1"/>
Although specified as type OctetString for compatibility with RADIUS
<xref target="RFC2865"/>,
the encoding of the Data field SHOULD also conform to
the rules for the UTF8String Data Format.
</t>
</section>
<section title="Framed-Interface-Id AVP">
<t>
The Framed-Interface-Id AVP (AVP Code 96) is of type Unsigned64 and
contains the IPv6 interface identifier to be configured for the user.
It MAY be used in authorization requests as a hint to the server that
a specific interface id is desired, but the server is not required to
honor the hint in the corresponding response.
</t>
</section>
<section title="Framed-IPv6-Prefix AVP">
<t>
The Framed-IPv6-Prefix AVP (AVP Code 97) is of type OctetString and
contains the IPv6 prefix to be configured for the user. One or more
AVPs MAY be used in authorization requests as a hint to the server
that specific IPv6 prefixes are desired, but the server is not
required to honor the hint in the corresponding response.
</t>
</section>
<section title="Framed-IPv6-Route AVP">
<t>
The Framed-IPv6-Route AVP (AVP Code 99) is of type UTF8String and
contains the ASCII routing information to be configured for the user
on the NAS. Zero or more of these AVPs MAY be present in an
authorization response.
<vspace blankLines="1"/>
The string MUST contain an IPv6 address prefix followed by a slash
and a decimal length specifier stating how many high order bits of
the prefix should be used. This is followed by a space, a gateway
address in hexadecimal notation, a space, and one or more metrics
separated by spaces; for example,
<list>
<t>"2000:0:0:106::/64 2000::106:a00:20ff:fe99:a998 1"</t>
</list>
Whenever the gateway address is the IPv6 unspecified address, the IP
address of the user SHOULD be used as the gateway address, such as in:
<list>
<t>"2000:0:0:106::/64 :: 1"</t>
</list>
</t>
</section>
<section title="Framed-IPv6-Pool AVP">
<t>
The Framed-IPv6-Pool AVP (AVP Code 100) is of type OctetString and
contains the name of an assigned pool that SHOULD be used to assign
an IPv6 prefix for the user. If the access device does not support
multiple prefix pools, it MUST ignore this AVP.
<vspace blankLines="1"/>
Although specified as type OctetString for compatibility with
RADIUS <xref target="RFC3162"/>, the encoding of the Data field SHOULD
also conform to the rules for the UTF8String Data Format.
</t>
</section>
</section>
<section title="IPX Access AVPs">
<t>
The AVPs defined in this section are used when the user requests, or
is being granted, access to an IPX network service <xref target="IPX"/>.
</t>
<section title="Framed-IPX-Network AVP">
<t>
The Framed-IPX-Network AVP (AVP Code 23) is of type Unsigned32 and
contains the IPX Network number to be configured for the user.
It MAY be used in an authorization request as a hint to the server that
a specific address is desired, but the server is not required to
honor the hint in the corresponding response.
<vspace blankLines="1"/>
Two addresses have special significance: 0xFFFFFFFF and 0xFFFFFFFE.
The value 0xFFFFFFFF indicates that the NAS should allow the user to
select an address (i.e., Negotiated). The value 0xFFFFFFFE indicates
that the NAS should select an address for the user (e.g., assign it
from a pool of one or more IPX networks kept by the NAS).
</t>
</section>
</section>
<section title="AppleTalk Network Access AVPs">
<t>
The AVPs defined in this section are used when the user requests, or
is being granted, access to an AppleTalk network <xref target="AppleTalk"/>.
</t>
<section title="Framed-AppleTalk-Link AVP">
<t>
The Framed-AppleTalk-Link AVP (AVP Code 37) is of type Unsigned32 and
contains the AppleTalk network number that should be used for the
serial link to the user, which is another AppleTalk router. This AVP
MUST only be present in an authorization response and is never used
when the user is not another router.
<vspace blankLines="1"/>
Despite the size of the field, values range from 0 to 65,535.
The special value of 0 indicates an unnumbered serial link.
A value of 1 to 65,535 means that the serial line between the NAS and the user
should be assigned that value as an AppleTalk network number.
</t>
</section>
<section title="Framed-AppleTalk-Network AVP">
<t>
The Framed-AppleTalk-Network AVP (AVP Code 38) is of type Unsigned32
and contains the AppleTalk Network number that the NAS should probe
to allocate an AppleTalk node for the user. This AVP MUST only be
present in an authorization response and is never used when the user
is not another router. Multiple instances of this AVP indicate that
the NAS may probe, using any of the network numbers specified.
<vspace blankLines="1"/>
Despite the size of the field, values range from 0 to 65,535. The
special value 0 indicates that the NAS should assign a network for
the user, using its default cable range. A value between 1 and
65,535 (inclusive) indicates to the AppleTalk Network that the NAS
should probe to find an address for the user.
</t>
</section>
<section title="Framed-AppleTalk-Zone AVP">
<t>
The Framed-AppleTalk-Zone AVP (AVP Code 39) is of type OctetString
and contains the AppleTalk Default Zone to be used for this user.
This AVP MUST only be present in an authorization response. Multiple
instances of this AVP in the same message are not allowed.
<vspace blankLines="1"/>
The codification of this field's allowed range is outside the scope of this specification.
</t>
</section>
</section>
<section title="AppleTalk Remote Access AVPs">
<t>
The AVPs defined in this section are used when the user requests, or
is being granted, access to the AppleTalk network via the AppleTalk
Remote Access Protocol <xref target="ARAP"/>
They are only present if the Framed-Protocol AVP <xref target="F-P-AVP"/>
is set to ARAP. Section 2.2 of RFC 2869 <xref target="RFC2869"/>
describes the operational use of these attributes.
</t>
<section title="ARAP-Features AVP">
<t>
The ARAP-Features AVP (AVP Code 71) is of type OctetString and MAY be
present in the AA-Accept message if the Framed-Protocol AVP is set to
the value of ARAP. See <xref target="RFC2869"/>
for more information about the
format of this AVP.
</t>
</section>
<section title="ARAP-Zone-Access AVP">
<t>
The ARAP-Zone-Access AVP (AVP Code 72) is of type Enumerated and MAY
be present in the AA-Accept message if the Framed-Protocol AVP is set
to the value of ARAP.
<vspace blankLines="1"/>
The supported values are listed in <xref target="RADIUSTypes"/>
and defined in <xref target="RFC2869"/>.
</t>
</section>
</section>
</section>
<section title="Non-Framed Access Authorization AVPs">
<t>
This section contains the authorization AVPs that are needed to
support terminal server functionality. AVPs defined in this section
MAY be present in a message if the Service-Type AVP was set to
"Login" or "Callback Login".
</t>
<section title="Login-IP-Host AVP">
<t>
The Login-IP-Host AVP (AVP Code 14) <xref target="RFC2865"/>
is of type OctetString
and contains the IPv4 address of a host with which to connect the
user when the Login-Service AVP is included. It MAY be used in an
AA-Request command as a hint to the Diameter Server that a specific
host is desired, but the Diameter Server is not required to honor the
hint in the AA-Answer.
<vspace blankLines="1"/>
Two addresses have special significance: all ones and 0. The value
of all ones indicates that the NAS SHOULD allow the user to select an
address. The value 0 indicates that the NAS SHOULD select a host to
connect the user to.
</t>
</section>
<section title="Login-IPv6-Host AVP">
<t>
The Login-IPv6-Host AVP (AVP Code 98) <xref target="RFC3162"/>
is of type
OctetString and contains the IPv6 address of a host with which to
connect the user when the Login-Service AVP is included. It MAY be
used in an AA-Request command as a hint to the Diameter Server that a
specific host is desired, but the Diameter Server is not required to
honor the hint in the AA-Answer.
<vspace blankLines="1"/>
Two addresses have special significance,
0xFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFF and 0. The value
0xFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFF indicates that the NAS SHOULD
allow the user to select an address. The value 0 indicates that the
NAS SHOULD select a host to connect the user to.
</t>
</section>
<section title="Login-Service AVP">
<t>
The Login-Service AVP (AVP Code 15) is of type Enumerated and
contains the service that should be used to connect the user to the
login host. This AVP SHOULD only be present in authorization responses.
The supported values are listed in <xref target="RFC2869"/>.
</t>
</section>
<section title="TCP Services" anchor="TCP-S">
<t>
The AVP described in the following section MAY be present if the
Login-Service AVP is set to Telnet, Rlogin, TCP Clear, or TCP Clear Quiet.
</t>
<section title="Login-TCP-Port AVP">
<t>
The Login-TCP-Port AVP (AVP Code 16) is of type Unsigned32 and
contains the TCP port with which the user is to be connected when the
Login-Service AVP is also present. This AVP SHOULD only be present
in authorization responses. The value MUST NOT be greater than 65,535.
</t>
</section>
</section>
<section title="LAT Services" anchor="LAT-S">
<t>
The AVPs described in this section MAY be present if the Login-Service AVP
is set to LAT <xref target="LAT"/>.
</t>
<section title="Login-LAT-Service AVP">
<t>
The Login-LAT-Service AVP (AVP Code 34) is of type OctetString and
contains the system with which the user is to be connected by LAT.
It MAY be used in an authorization request as a hint to the server
that a specific service is desired, but the server is not required to
honor the hint in the corresponding response. This AVP MUST only be
present in the response if the Login-Service AVP states that LAT is desired.
<vspace blankLines="1"/>
Administrators use this service attribute when dealing with clustered
systems, such as a VAX or Alpha cluster. In these environments,
several different time-sharing hosts share the same resources (disks,
printers, etc.), and administrators often configure each host to
offer access (service) to each of the shared resources. In this
case, each host in the cluster advertises its services through LAT broadcasts.
<vspace blankLines="1"/>
Sophisticated users often know which service providers (machines) are
faster and tend to use a node name when initiating a LAT connection.
Some administrators want particular users to use certain machines as
a primitive form of load balancing (although LAT knows how to do load balancing itself).
<vspace blankLines="1"/>
The String field contains the identity of the LAT service to use.
The LAT Architecture allows this string to contain $ (dollar),
- (hyphen), . (period), _ (underscore), numerics, upper- and lowercase
alphabetics, and the ISO Latin-1 character set
extension <xref target="ISO.8859-1.1987"/>.
All LAT string comparisons are case insensitive.
</t>
</section>
<section title="Login-LAT-Node AVP">
<t>
The Login-LAT-Node AVP (AVP Code 35) is of type OctetString and
contains the Node with which the user is to be automatically
connected by LAT. It MAY be used in an authorization request as a
hint to the server that a specific LAT node is desired, but the
server is not required to honor the hint in the corresponding
response. This AVP MUST only be present in a response if the Login-Service-Type
AVP is set to LAT.
<vspace blankLines="1"/>
The String field contains the identity of the LAT service to use.
The LAT Architecture allows this string to contain $ (dollar),
- (hyphen), . (period), _ (underscore), numerics, upper- and lowercase
alphabetics, and the ISO Latin-1 character set
extension <xref target="ISO.8859-1.1987"/>.
All LAT string comparisons are case insensitive.
</t>
</section>
<section title="Login-LAT-Group AVP">
<t>
The Login-LAT-Group AVP (AVP Code 36) is of type OctetString and
contains a string identifying the LAT group codes this user is
authorized to use. It MAY be used in an authorization request as a
hint to the server that a specific group is desired, but the server
is not required to honor the hint in the corresponding response.
This AVP MUST only be present in a response if the Login-Service-Type
AVP is set to LAT.
<vspace blankLines="1"/>
LAT supports 256 different group codes, which LAT uses as a form of
access rights. LAT encodes the group codes as a 256-bit bitmap.
<vspace blankLines="1"/>
Administrators can assign one or more of the group code bits at the
LAT service provider; it will only accept LAT connections that have
these group codes set in the bitmap. The administrators assign a
bitmap of authorized group codes to each user. LAT gets these from
the operating system and uses them in its requests to the service providers.
<vspace blankLines="1"/>
The codification of the range of allowed usage of this field is
outside the scope of this specification.
</t>
</section>
<section title="Login-LAT-Port AVP">
<t>
The Login-LAT-Port AVP (AVP Code 63) is of type OctetString and
contains the Port with which the user is to be connected by LAT. It
MAY be used in an authorization request as a hint to the server that
a specific port is desired, but the server is not required to honor
the hint in the corresponding response. This AVP MUST only be
present in a response if the Login-Service-Type AVP is set to LAT.
<vspace blankLines="1"/>
The String field contains the identity of the LAT service to use.
The LAT Architecture allows this string to contain $ (dollar),
- (hyphen), . (period), _ (underscore), numerics, upper- and lower-case
alphabetics, and the ISO Latin-1 character set
extension <xref target="ISO.8859-1.1987"/>.
<vspace blankLines="1"/>
All LAT string comparisons are case insensitive.
</t>
</section>
</section>
</section>
</section>
<section title="NAS Tunneling AVPs" anchor="TUNNELING-AVPS">
<t>
Some NASes support compulsory tunnel services in which the incoming
connection data is conveyed by an encapsulation method to a gateway
elsewhere in the network. This is typically transparent to the
service user, and the tunnel characteristics may be described by the
remote AAA server, based on the user's authorization information.
Several tunnel characteristics may be returned, and the NAS
implementation may choose one.
See <xref target="RFC2868"/> and <xref target="RFC2867"/> for further information.
<vspace blankLines="1"/>
The following table gives the possible flag values for the session level AVPs
and specifies whether the AVP MAY be encrypted.
<figure align="left" suppress-title="true"><artwork><![CDATA[
+---------------------+
| AVP Flag rules |
|----+-----+----+-----|----+
| | |SHLD| MUST| |
Attribute Name Section Defined |MUST| MAY | NOT| NOT|Encr|
-----------------------------------------|----+-----+----+-----|----|
Tunneling 4.5.1 | M | P | | V | N |
Tunnel-Type 4.5.2 | M | P | | V | Y |
Tunnel-Medium-Type 4.5.3 | M | P | | V | Y |
Tunnel-Client-Endpoint 4.5.4 | M | P | | V | Y |
Tunnel-Server-Endpoint 4.5.5 | M | P | | V | Y |
Tunnel-Password 4.5.6 | M | P | | V | Y |
Tunnel-Private-Group-Id 4.5.7 | M | P | | V | Y |
Tunnel-Assignment-Id 4.5.8 | M | P | | V | Y |
Tunnel-Preference 4.5.9 | M | P | | V | Y |
Tunnel-Client-Auth-Id 4.5.10 | M | P | | V | Y |
Tunnel-Server-Auth-Id 4.5.11 | M | P | | V | Y |
-----------------------------------------|----+-----+----+-----|----|
]]> </artwork></figure>
</t>
<section title="Tunneling AVP">
<t>
The Tunneling AVP (AVP Code 401) is of type Grouped and contains the
following AVPs, used to describe a compulsory tunnel service
(<xref target="RFC2868"/>, <xref target="RFC2867"/>).
Its data field has the following ABNF grammar:
<figure align="left" suppress-title="true"><artwork><![CDATA[
Tunneling ::= < AVP Header: 401 >
{ Tunnel-Type }
{ Tunnel-Medium-Type }
{ Tunnel-Client-Endpoint }
{ Tunnel-Server-Endpoint }
[ Tunnel-Preference ]
[ Tunnel-Client-Auth-Id ]
[ Tunnel-Server-Auth-Id ]
[ Tunnel-Assignment-Id ]
[ Tunnel-Password ]
[ Tunnel-Private-Group-Id ]
]]> </artwork></figure>
</t>
</section>
<section title="Tunnel-Type AVP" anchor="T-T-AVP">
<t>
The Tunnel-Type AVP (AVP Code 64) is of type Enumerated and contains
the tunneling protocol(s) to be used (in the case of a tunnel
initiator) or in use (in the case of a tunnel terminator). It MAY be
used in an authorization request as a hint to the server that a
specific tunnel type is desired, but the server is not required to
honor the hint in the corresponding response.
<vspace blankLines="1"/>
The Tunnel-Type AVP SHOULD also be included in ACR messages.
<vspace blankLines="1"/>
A tunnel initiator is not required to implement any of these tunnel
types. If a tunnel initiator receives a response that contains only
unknown or unsupported Tunnel-Types, the tunnel initiator MUST behave
as though a response were received with the Result-Code indicating a failure.
<vspace blankLines="1"/>
The supported values are listed in <xref target="RADIUSTypes"/>.
</t>
</section>
<section title="Tunnel-Medium-Type AVP" anchor="T-M-T-AVP">
<t>
The Tunnel-Medium-Type AVP (AVP Code 65) is of type Enumerated and
contains the transport medium to use when creating a tunnel for
protocols (<xref target="RFC2661">such as L2TP</xref>)
that can operate over multiple transports.
It MAY be used in an authorization request as a hint to the server
that a specific medium is desired, but the server is not required to
honor the hint in the corresponding response.
<vspace blankLines="1"/>
The supported values are listed in <xref target="RADIUSTypes"/>.
</t>
</section>
<section title="Tunnel-Client-Endpoint AVP" anchor="T-C-E-AVP">
<t>
The Tunnel-Client-Endpoint AVP (AVP Code 66) is of type UTF8String
and contains the address of the initiator end of the tunnel. It MAY
be used in an authorization request as a hint to the server that a
specific endpoint is desired, but the server is not required to honor
the hint in the corresponding response.
This AVP SHOULD be included in the corresponding ACR
messages, in which case it indicates the address from which the
tunnel was initiated. This AVP, along with the
Tunnel-Server-Endpoint (<xref target="T-S-E-AVP"/>)
and Session-Id AVPs
(<xref target="I-D.ietf-dime-rfc3588bis"/>, Section 8.8), can be used to provide a globally
unique means to identify a tunnel for accounting and auditingpurposes.
<vspace blankLines="1"/>
If the value of the Tunnel-Medium-Type AVP (<xref target="T-M-T-AVP"/>)
is IPv4 (1), then this string is either the
fully qualified domain name (FQDN) of the tunnel client machine, or a
"dotted-decimal" IP address. Implementations MUST support the
dotted-decimal format and SHOULD support the FQDN format for IP addresses.
<vspace blankLines="1"/>
If Tunnel-Medium-Type is IPv6 (2), then this string is either the
FQDN of the tunnel client machine, or a text representation of the
address in either the preferred or alternate form <xref target="RFC3516"/>.
Conforming implementations MUST support the preferred form and SHOULD
support both the alternate text form and the FQDN format for IPv6 addresses.
<vspace blankLines="1"/>
If Tunnel-Medium-Type is neither IPv4 nor IPv6, then this string is a
tag referring to configuration data local to the Diameter client that
describes the interface or medium-specific client address to use.
</t>
</section>
<section title="Tunnel-Server-Endpoint AVP" anchor="T-S-E-AVP">
<t>
The Tunnel-Server-Endpoint AVP (AVP Code 67) is of type UTF8String
and contains the address of the server end of the tunnel. It MAY be
used in an authorization request as a hint to the server that a
specific endpoint is desired, but the server is not required to honor
the hint in the corresponding response.
<vspace blankLines="1"/>
This AVP SHOULD be included in the corresponding ACR
messages, in which case it indicates the address from which the
tunnel was initiated. This AVP, along with the
Tunnel-Client-Endpoint (<xref target="T-C-E-AVP"/>)
and Session-Id AVP (<xref target="I-D.ietf-dime-rfc3588bis"/>, Section 8.8),
can be used to provide a globally unique means to identify a tunnel for accounting
and auditing purposes.
<vspace blankLines="1"/>
If Tunnel-Medium-Type is IPv4 (1), then this string is either the
fully qualified domain name (FQDN) of the tunnel server machine, or a
"dotted-decimal" IP address. Implementations MUST support the
dotted-decimal format and SHOULD support the FQDN format for IP addresses.
<vspace blankLines="1"/>
If Tunnel-Medium-Type is IPv6 (2), then this string is either the
FQDN of the tunnel server machine, or a text representation of the
address in either the preferred or alternate form <xref target="RFC3516"/>.
Implementations MUST support the preferred form and SHOULD support
both the alternate text form and the FQDN format for IPv6 addresses.
<vspace blankLines="1"/>
If Tunnel-Medium-Type is not IPv4 or IPv6, this string is a tag
referring to configuration data local to the Diameter client that
describes the interface or medium-specific server address to use.
</t>
</section>
<section title="Tunnel-Password AVP">
<t>
The Tunnel-Password AVP (AVP Code 69) is of type OctetString and may
contain a password to be used to authenticate to a remote server.
<vspace blankLines="1"/>
The Tunnel-Password AVP contains sensitive information. This value
is not protected in the same manner as RADIUS <xref target="RFC2868"/>.
Diameter messages are secured by
using IPsec or TLS <xref target="I-D.ietf-dime-rfc3588bis"/>.
The Tunnel-Password AVP SHOULD NOT be used in untrusted
proxy environments without encrypting it by using end-to-end security techniques.
</t>
</section>
<section title="Tunnel-Private-Group-Id AVP">
<t>
The Tunnel-Private-Group-Id AVP (AVP Code 81) is of type OctetString
and contains the group Id for a particular tunneled session. The
Tunnel-Private-Group-Id AVP MAY be included in an authorization
request if the tunnel initiator can predetermine the group resulting
from a particular connection. It SHOULD be included in the
authorization response if this tunnel session is to be treated as
belonging to a particular private group. Private groups may be used
to associate a tunneled session with a particular group of users.
For example, it MAY be used to facilitate routing of unregistered IP
addresses through a particular interface. This AVP SHOULD be
included in the ACR messages that pertain to the
tunneled session.
</t>
</section>
<section title="Tunnel-Assignment-Id AVP">
<t>
The Tunnel-Assignment-Id AVP (AVP Code 82) is of type OctetString and
is used to indicate to the tunnel initiator the particular tunnel to
which a session is to be assigned.
Some tunneling protocols, such as PPTP <xref target="RFC2637"/>
and L2TP <xref target="RFC2661"/>,
allow for sessions between the same two tunnel
endpoints to be multiplexed over the same tunnel and also for a given
session to use its own dedicated tunnel. This attribute provides a
mechanism for Diameter to inform the tunnel initiator (e.g., PAC,
LAC) whether to assign the session to a multiplexed tunnel or to a
separate tunnel. Furthermore, it allows for sessions sharing
multiplexed tunnels to be assigned to different multiplexed tunnels.
<vspace blankLines="1"/>
A particular tunneling implementation may assign differing
characteristics to particular tunnels. For example, different
tunnels may be assigned different QoS parameters. Such tunnels may
be used to carry either individual or multiple sessions. The
Tunnel-Assignment-Id attribute thus allows the Diameter server to
indicate that a particular session is to be assigned to a tunnel
providing an appropriate level of service. It is expected that any
QoS-related Diameter tunneling attributes defined in the future
accompanying this one will be associated by the tunnel initiator with
the Id given by this attribute. In the meantime, any semantic given
to a particular Id string is a matter left to local configuration in the tunnel initiator.
<vspace blankLines="1"/>
The Tunnel-Assignment-Id AVP is of significance only to Diameter and
the tunnel initiator. The Id it specifies is only intended to be of
local use to Diameter and the tunnel initiator. The Id assigned by
the tunnel initiator is not conveyed to the tunnel peer.
<vspace blankLines="1"/>
This attribute MAY be included in authorization responses. The
tunnel initiator receiving this attribute MAY choose to ignore it and
to assign the session to an arbitrary multiplexed or non-multiplexed
tunnel between the desired endpoints. This AVP SHOULD also be
included in the Accounting-Request messages pertaining to the
tunneled session.
<vspace blankLines="1"/>
If a tunnel initiator supports the Tunnel-Assignment-Id AVP, then it
should assign a session to a tunnel in the following manner:
<list style="symbols">
<t>
If this AVP is present and a tunnel exists between the
specified endpoints with the specified Id, then the session
should be assigned to that tunnel.
</t>
<t>
If this AVP is present and no tunnel exists between the
specified endpoints with the specified Id, then a new tunnel
should be established for the session and the specified Id
should be associated with the new tunnel.
</t>
<t>
If this AVP is not present, then the session is assigned to an
unnamed tunnel. If an unnamed tunnel does not yet exist
between the specified endpoints, then it is established and
used for this session and for subsequent ones established
without the Tunnel-Assignment-Id attribute. A tunnel initiator
MUST NOT assign a session for which a Tunnel-Assignment-Id AVP
was not specified to a named tunnel (i.e., one that was
initiated by a session specifying this AVP).
</t>
</list>
Note that the same Id may be used to name different tunnels if these
tunnels are between different endpoints.
</t>
</section>
<section title="Tunnel-Preference AVP">
<t>
The Tunnel-Preference AVP (AVP Code 83) is of type Unsigned32 and is
used to identify the relative preference assigned to each tunnel when
more than one set of tunneling AVPs is returned within separate
Grouped-AVP AVPs. It MAY be used in an authorization request as a
hint to the server that a specific preference is desired, but the
server is not required to honor the hint in the corresponding response.
<vspace blankLines="1"/>
For example, suppose that AVPs describing two tunnels are returned by
the server, one with a Tunnel-Type of PPTP and the other with a
Tunnel-Type of L2TP. If the tunnel initiator supports only one of
the Tunnel-Types returned, it will initiate a tunnel of that type.
If, however, it supports both tunnel protocols, it SHOULD use the
value of the Tunnel-Preference AVP to decide which tunnel should be
started. The tunnel with the lowest numerical value in the Value
field of this AVP SHOULD be given the highest preference. The values
assigned to two or more instances of the Tunnel-Preference AVP within
a given authorization response MAY be identical. In this case, the
tunnel initiator SHOULD use locally configured metrics to decidewhich set of AVPs to use.
</t>
</section>
<section title="Tunnel-Client-Auth-Id AVP">
<t>
The Tunnel-Client-Auth-Id AVP (AVP Code 90) is of type UTF8String and
specifies the name used by the tunnel initiator during the
authentication phase of tunnel establishment. It MAY be used in an
authorization request as a hint to the server that a specific
preference is desired, but the server is not required to honor the
hint in the corresponding response. This AVP MUST be present in the
authorization response if an authentication name other than the
default is desired. This AVP SHOULD be included in the ACR messages
pertaining to the tunneled session.
</t>
</section>
<section title="Tunnel-Server-Auth-Id AVP">
<t>
The Tunnel-Server-Auth-Id AVP (AVP Code 91) is of type UTF8String and
specifies the name used by the tunnel terminator during the
authentication phase of tunnel establishment. It MAY be used in an
authorization request as a hint to the server that a specific
preference is desired, but the server is not required to honor the
hint in the corresponding response. This AVP MUST be present in the
authorization response if an authentication name other than the
default is desired. This AVP SHOULD be included in the ACR messages
pertaining to the tunneled session.
</t>
</section>
</section>
<section title="NAS Accounting AVPs" anchor="ACCT-AVP">
<t>
Applications implementing this specification use Diameter Accounting
(as defined in <xref target="I-D.ietf-dime-rfc3588bis"/>)
and the AVPs in the following section.
Service-specific AVP usage is defined in the tables in <xref target="A-O-T"/>.
<vspace blankLines="1"/>
If accounting is active, Accounting Request (ACR) messages SHOULD be
sent after the completion of any Authentication or Authorization
transaction and at the end of a Session. The value of the Accounting-Record-Type
AVP <xref target="I-D.ietf-dime-rfc3588bis"/>
indicates the type of event. All other AVPs identify the
session and provide additional information relevant to the event.
<vspace blankLines="1"/>
The successful completion of the first Authentication or
Authorization transaction SHOULD cause a START_RECORD to be sent. If
additional Authentications or Authorizations occur in later
transactions, the first exchange should generate a START_RECORD, and
the later an INTERIM_RECORD. For a given session, there MUST only be
one set of matching START and STOP records, with any number of
INTERIM_RECORDS in between, or one EVENT_RECORD indicating the reason
a session wasn't started.
<vspace blankLines="1"/>
The following table gives the possible flag values for the session level AVPs
and specifies whether the AVP MAY be encrypted.
<figure align="left" suppress-title="true"><artwork><![CDATA[
+---------------------+
| AVP Flag rules |
|----+-----+----+-----|----+
Section | | |SHLD| MUST| |
Attribute Name Defined |MUST| MAY | NOT| NOT|Encr|
-----------------------------------------|----+-----+----+-----|----|
Accounting-Input-Octets 4.6.1 | M | P | | V | Y |
Accounting-Output-Octets 4.6.2 | M | P | | V | Y |
Accounting-Input-Packets 4.6.3 | M | P | | V | Y |
Accounting-Output-Packets 4.6.4 | M | P | | V | Y |
Acct-Session-Time 4.6.5 | M | P | | V | Y |
Acct-Authentic 4.6.6 | M | P | | V | Y |
Accounting-Auth-Method 4.6.7 | M | P | | V | Y |
Acct-Delay-Time 4.6.8 | M | P | | V | Y |
Acct-Link-Count 4.6.9 | M | P | | V | Y |
Acct-Tunnel-Connection 4.6.10 | M | P | | V | Y |
Acct-Tunnel-Packets-Lost 4.6.11 | M | P | | V | Y |
-----------------------------------------|----+-----+----+-----|----|
]]></artwork></figure>
</t>
<section title="Accounting-Input-Octets AVP">
<t>
The Accounting-Input-Octets AVP (AVP Code 363) is of type Unsigned64
and contains the number of octets received from the user.
<vspace blankLines="1"/>
For NAS usage, this AVP indicates how many octets have been received
from the port in the course of this session. It can only be present
in ACR messages with an Accounting-Record-Type <xref target="I-D.ietf-dime-rfc3588bis"/>
of INTERIM_RECORD or STOP_RECORD.
</t>
</section>
<section title="Accounting-Output-Octets AVP">
<t>
The Accounting-Output-Octets AVP (AVP Code 364) is of type Unsigned64
and contains the number of octets sent to the user.
<vspace blankLines="1"/>
For NAS usage, this AVP indicates how many octets have been sent to
the port in the course of this session. It can only be present in
ACR messages with an Accounting-Record-Type of INTERIM_RECORD or
STOP_RECORD.
</t>
</section>
<section title="Accounting-Input-Packets AVP">
<t>
The Accounting-Input-Packets (AVP Code 365) is of type Unsigned64 and
contains the number of packets received from the user.
<vspace blankLines="1"/>
For NAS usage, this AVP indicates how many packets have been received
from the port over the course of a session being provided to a Framed
User. It can only be present in ACR messages with an Accounting-Record-Type
of INTERIM_RECORD or STOP_RECORD.
</t>
</section>
<section title="Accounting-Output-Packets AVP">
<t>
The Accounting-Output-Packets (AVP Code 366) is of type Unsigned64
and contains the number of IP packets sent to the user.
<vspace blankLines="1"/>
For NAS usage, this AVP indicates how many packets have been sent to
the port over the course of a session being provided to a Framed
User. It can only be present in ACR messages with an Accounting-Record-Type
of INTERIM_RECORD or STOP_RECORD.
</t>
</section>
<section title="Acct-Session-Time AVP">
<t>
The Acct-Session-Time AVP (AVP Code 46) is of type Unsigned32 and
indicates the length of the current session in seconds. It can only
be present in ACR messages with an Accounting-Record-Type of
INTERIM_RECORD or STOP_RECORD.
</t>
</section>
<section title="Acct-Authentic AVP">
<t>
The Acct-Authentic AVP (AVP Code 45) is of type Enumerated and
specifies how the user was authenticated. The supported values are
listed in <xref target="RADIUSTypes"/>.
</t>
</section>
<section title="Accounting-Auth-Method AVP" anchor="A-A-M-AVP">
<t>
The Accounting-Auth-Method AVP (AVP Code 406) is of type Enumerated.
A NAS MAY include this AVP in an Accounting-Request message to
indicate the method used to authenticate the user. (Note that this AVP
is semantically equivalent, and the supported values are identical, to the
Microsoft MS-Acct-Auth-Type vendor-specific RADIUS attribute <xref target="RFC2548"/>).
</t>
</section>
<section title="Acct-Delay-Time AVP">
<t>
The Acct-Delay-Time AVP (AVP Code 41) is of type Unsigned32 and
indicates the number of seconds the Diameter client has been trying
to send the Accounting-Request (ACR). The accounting server may
subtract this value from the time when the ACR arrives at the server
to calculate the approximate time of the event that caused the ACR to
be generated.
<vspace blankLines="1"/>
This AVP is not used for retransmissions at the transport level (TCP
or SCTP). Rather, it may be used when an ACR command cannot be
transmitted because there is no appropriate peer to transmit it to or
was rejected because it could not be delivered. In these cases, the
command MAY be buffered and transmitted later, when an appropriate
peer-connection is available or after sufficient time has passed that
the destination-host may be reachable and operational. If the ACR is
re-sent in this way, the Acct-Delay-Time AVP SHOULD be included. The
value of this AVP indicates the number of seconds that elapsed
between the time of the first attempt at transmission and the current attempt.
</t>
</section>
<section title="Acct-Link-Count AVP">
<t>
The Acct-Link-Count AVP (AVP Code 51) is of type Unsigned32 and
indicates the total number of links that have been active (current or
closed) in a given multilink session at the time the accounting
record is generated. This AVP MAY be included in Accounting-Requests
for any session that may be part of a multilink service.
<vspace blankLines="1"/>
The Acct-Link-Count AVP may be used to make it easier for an
accounting server to know when it has all the records for a given
multilink service. When the number of Accounting-Requests received
with Accounting-Record-Type = STOP_RECORD and with the same
Acct-Multi-Session-Id and unique Session-Ids equals the largest value of
Acct-Link-Count seen in those Accounting-Requests, all STOP_RECORD
Accounting-Requests for that multilink service have been received.
<vspace blankLines="1"/>
The following example, showing eight Accounting-Requests, illustrates
how the Acct-Link-Count AVP is used. In the table below, only the
relevant AVPs are shown, although additional AVPs containing
accounting information will be present in the
Accounting-Requests.
<figure align="center" suppress-title="true"><artwork><![CDATA[
Acct-Multi- Accounting- Acct-
Session-Id Session-Id Record-Type Link-Count
--------------------------------------------------------
"...10" "...10" START_RECORD 1
"...10" "...11" START_RECORD 2
"...10" "...11" STOP_RECORD 2
"...10" "...12" START_RECORD 3
"...10" "...13" START_RECORD 4
"...10" "...12" STOP_RECORD 4
"...10" "...13" STOP_RECORD 4
"...10" "...10" STOP_RECORD 4
]]></artwork></figure>
</t>
</section>
<section title="Acct-Tunnel-Connection AVP">
<t>
The Acct-Tunnel-Connection AVP (AVP Code 68) is of type OctetString
and contains the identifier assigned to the tunnel session. This
AVP, along with the Tunnel-Client-Endpoint (<xref target="T-C-E-AVP"/>)
and Tunnel-Server-Endpoint (<xref target="T-S-E-AVP"/>)
AVPs, may be used to provide a means to uniquely identify a tunnel
session for auditing purposes.
<vspace blankLines="1"/>
The format of the identifier in this AVP depends upon the value of
the Tunnel-Type AVP (<xref target="T-T-AVP"/>).
For example, to identify an L2TP tunnel
connection fully, the L2TP Tunnel Id and Call Id might be encoded in
this field. The exact encoding of this field is implementation dependent.
</t>
</section>
<section title="Acct-Tunnel-Packets-Lost AVP">
<t>
The Acct-Tunnel-Packets-Lost AVP (AVP Code 86) is of type Unsigned32
and contains the number of packets lost on a given tunnel.
</t>
</section>
</section>
</section>
<section title="AVP Occurrence Tables" anchor="A-O-T">
<t>
The following tables present the AVPs used by NAS applications in NAS
messages and specify in which Diameter messages they MAY or MAY NOT
be present. Messages and AVPs defined in the base
Diameter protocol <xref target="I-D.ietf-dime-rfc3588bis"/>
are not described in this document. Note that AVPs that can only be present within a Grouped
AVP are not represented in this table.
<vspace blankLines="1"/>
The table uses the following symbols:
<?rfc subcompact="true"?>
<list>
<t>
<list style="hanging" hangIndent="5">
<t hangText="0">The AVP MUST NOT be present in the message.</t>
<t hangText="0+">Zero or more instances of the AVP MAY be present in the message.</t>
<t hangText="0-1">Zero or one instance of the AVP MAY be present in the message.</t>
<t hangText="1">Exactly one instance of the AVP MUST be present in the message.</t>
</list>
</t>
</list>
<?rfc subcompact="false"?>
</t>
<section title="AA-Request/Answer AVP Table">
<t>
The table in this section is limited to the Command Codes defined in this specification.
<figure align="center" suppress-title="true"><artwork><![CDATA[
+-----------+
| Command |
|-----+-----+
AVP Name | AAR | AAA |
------------------------------|-----+-----+
Acct-Interim-Interval | 0 | 0-1 |
ARAP-Challenge-Response | 0 | 0-1 |
ARAP-Features | 0 | 0-1 |
ARAP-Password | 0-1 | 0 |
ARAP-Security | 0-1 | 0-1 |
ARAP-Security-Data | 0+ | 0+ |
ARAP-Zone-Access | 0 | 0-1 |
Auth-Application-Id | 1 | 1 |
Auth-Grace-Period | 0-1 | 0-1 |
Auth-Request-Type | 1 | 1 |
Auth-Session-State | 0-1 | 0-1 |
Authorization-Lifetime | 0-1 | 0-1 |
------------------------------|-----+-----+
]]></artwork></figure>
<?rfc needLines="47"?>
<figure align="center" suppress-title="true"><artwork><![CDATA[
+-----------+
| Command |
|-----+-----+
Attribute Name | AAR | AAA |
------------------------------|-----+-----+
Callback-Id | 0 | 0-1 |
Callback-Number | 0-1 | 0-1 |
Called-Station-Id | 0-1 | 0 |
Calling-Station-Id | 0-1 | 0 |
CHAP-Auth | 0-1 | 0 |
CHAP-Challenge | 0-1 | 0 |
Class | 0 | 0+ |
Configuration-Token | 0 | 0+ |
Connect-Info | 0+ | 0 |
Destination-Host | 0-1 | 0 |
Destination-Realm | 1 | 0 |
Error-Message | 0 | 0-1 |
Error-Reporting-Host | 0 | 0-1 |
Failed-AVP | 0+ | 0+ |
Filter-Id | 0 | 0+ |
Framed-Appletalk-Link | 0 | 0-1 |
Framed-Appletalk-Network | 0 | 0+ |
Framed-Appletalk-Zone | 0 | 0-1 |
Framed-Compression | 0+ | 0+ |
Framed-Interface-Id | 0-1 | 0-1 |
Framed-IP-Address | 0-1 | 0-1 |
Framed-IP-Netmask | 0-1 | 0-1 |
Framed-IPv6-Prefix | 0+ | 0+ |
Framed-IPv6-Pool | 0 | 0-1 |
Framed-IPv6-Route | 0 | 0+ |
Framed-IPX-Network | 0 | 0-1 |
Framed-MTU | 0-1 | 0-1 |
Framed-Pool | 0 | 0-1 |
Framed-Protocol | 0-1 | 0-1 |
Framed-Route | 0 | 0+ |
Framed-Routing | 0 | 0-1 |
Idle-Timeout | 0 | 0-1 |
Login-IP-Host | 0+ | 0+ |
Login-IPv6-Host | 0+ | 0+ |
Login-LAT-Group | 0-1 | 0-1 |
Login-LAT-Node | 0-1 | 0-1 |
Login-LAT-Port | 0-1 | 0-1 |
Login-LAT-Service | 0-1 | 0-1 |
Login-Service | 0 | 0-1 |
Login-TCP-Port | 0 | 0-1 |
Multi-Round-Time-Out | 0 | 0-1 |
------------------------------|-----+-----+
]]></artwork></figure>
<?rfc needLines="37"?>
<figure align="center" suppress-title="true"><artwork><![CDATA[
+-----------+
| Command |
|-----+-----+
Attribute Name | AAR | AAA |
------------------------------|-----+-----+
NAS-Filter-Rule | 0 | 0+ |
NAS-Identifier | 0-1 | 0 |
NAS-IP-Address | 0-1 | 0 |
NAS-IPv6-Address | 0-1 | 0 |
NAS-Port | 0-1 | 0 |
NAS-Port-Id | 0-1 | 0 |
NAS-Port-Type | 0-1 | 0 |
Origin-AAA-Protocol | 0-1 | 0-1 |
Origin-Host | 1 | 1 |
Origin-Realm | 1 | 1 |
Origin-State-Id | 0-1 | 0-1 |
Originating-Line-Info | 0-1 | 0 |
Password-Retry | 0 | 0-1 |
Port-Limit | 0-1 | 0-1 |
Prompt | 0 | 0-1 |
Proxy-Info | 0+ | 0+ |
QoS-Filter-Rule | 0 | 0+ |
Re-Auth-Request-Type | 0 | 0-1 |
Redirect-Host | 0 | 0+ |
Redirect-Host-Usage | 0 | 0-1 |
Redirect-Max-Cache-Time | 0 | 0-1 |
Reply-Message | 0 | 0+ |
Result-Code | 0 | 1 |
Route-Record | 0+ | 0+ |
Service-Type | 0-1 | 0-1 |
Session-Id | 1 | 1 |
Session-Timeout | 0 | 0-1 |
State | 0-1 | 0-1 |
Tunneling | 0+ | 0+ |
User-Name | 0-1 | 0-1 |
User-Password | 0-1 | 0 |
------------------------------|-----+-----+
]]></artwork></figure>
</t>
</section>
<section title="Accounting AVP Tables">
<t>
The tables in this section are used to show which AVPs defined in
this document are to be present and used in NAS application
Accounting messages. These AVPs are defined in this document, as
well as in <xref target="I-D.ietf-dime-rfc3588bis"/>
and <xref target="RFC2866"/>.
</t>
<section title="Framed Access Accounting AVP Table">
<t>
The table in this section is used when the Service-Type AVP (<xref target="S-T-AVP"/>)
specifies Framed Access.
<?rfc needLines="38"?>
<figure align="center" suppress-title="true"><artwork><![CDATA[
+-----------+
| Command |
|-----+-----+
Attribute Name | ACR | ACA |
---------------------------------------|-----+-----+
Accounting-Auth-Method | 0-1 | 0 |
Accounting-Input-Octets | 1 | 0 |
Accounting-Input-Packets | 1 | 0 |
Accounting-Output-Octets | 1 | 0 |
Accounting-Output-Packets | 1 | 0 |
Accounting-Record-Number | 0-1 | 0-1 |
Accounting-Record-Type | 1 | 1 |
Accounting-Realtime-Required | 0-1 | 0-1 |
Accounting-Sub-Session-Id | 0-1 | 0-1 |
Acct-Application-Id | 0-1 | 0-1 |
Acct-Session-Id | 1 | 0-1 |
Acct-Multi-Session-Id | 0-1 | 0-1 |
Acct-Authentic | 1 | 0 |
Acct-Delay-Time | 0-1 | 0 |
Acct-Interim-Interval | 0-1 | 0-1 |
Acct-Link-Count | 0-1 | 0 |
Acct-Session-Time | 1 | 0 |
Acct-Tunnel-Connection | 0-1 | 0 |
Acct-Tunnel-Packets-Lost | 0-1 | 0 |
Authorization-Lifetime | 0-1 | 0 |
Callback-Id | 0-1 | 0 |
Callback-Number | 0-1 | 0 |
Called-Station-Id | 0-1 | 0 |
Calling-Station-Id | 0-1 | 0 |
Class | 0+ | 0+ |
Connection-Info | 0+ | 0 |
Destination-Host | 0-1 | 0 |
Destination-Realm | 1 | 0 |
Event-Timestamp | 0-1 | 0-1 |
Error-Message | 0 | 0-1 |
Error-Reporting-Host | 0 | 0-1 |
Failed-AVP | 0 | 0+ |
---------------------------------------|-----+-----+
]]></artwork></figure>
<?rfc needLines="47"?>
<figure align="center" suppress-title="true"><artwork><![CDATA[
+-----------+
| Command |
|-----+-----+
Attribute Name | ACR | ACA |
---------------------------------------|-----+-----+
Framed-AppleTalk-Link | 0-1 | 0 |
Framed-AppleTalk-Network | 0-1 | 0 |
Framed-AppleTalk-Zone | 0-1 | 0 |
Framed-Compression | 0-1 | 0 |
Framed-IP-Address | 0-1 | 0 |
Framed-IP-Netmask | 0-1 | 0 |
Framed-IPv6-Prefix | 0+ | 0 |
Framed-IPv6-Pool | 0-1 | 0 |
Framed-IPX-Network | 0-1 | 0 |
Framed-MTU | 0-1 | 0 |
Framed-Pool | 0-1 | 0 |
Framed-Protocol | 0-1 | 0 |
Framed-Route | 0-1 | 0 |
Framed-Routing | 0-1 | 0 |
NAS-Filter-Rule | 0+ | 0 |
NAS-Identifier | 0-1 | 0-1 |
NAS-IP-Address | 0-1 | 0-1 |
NAS-IPv6-Address | 0-1 | 0-1 |
NAS-Port | 0-1 | 0-1 |
NAS-Port-Id | 0-1 | 0-1 |
NAS-Port-Type | 0-1 | 0-1 |
Origin-AAA-Protocol | 0-1 | 0-1 |
Origin-Host | 1 | 1 |
Origin-Realm | 1 | 1 |
Origin-State-Id | 0-1 | 0-1 |
Originating-Line-Info | 0-1 | 0 |
Proxy-Info | 0+ | 0+ |
QoS-Filter-Rule | 0+ | 0 |
Route-Record | 0+ | 0+ |
Result-Code | 0 | 1 |
Service-Type | 0-1 | 0-1 |
Session-Id | 1 | 1 |
Termination-Cause | 0-1 | 0-1 |
Tunnel-Assignment-Id | 0-1 | 0 |
Tunnel-Client-Endpoint | 0-1 | 0 |
Tunnel-Medium-Type | 0-1 | 0 |
Tunnel-Private-Group-Id | 0-1 | 0 |
Tunnel-Server-Endpoint | 0-1 | 0 |
Tunnel-Type | 0-1 | 0 |
User-Name | 0-1 | 0-1 |
Vendor-Specific-Application-Id | 0-1 | 0-1 |
---------------------------------------|-----+-----+
]]></artwork></figure>
</t>
</section>
<section title="Non-Framed Access Accounting AVP Table">
<t>
The table in this section is used when the Service-Type AVP (<xref target="S-T-AVP"/>)
specifies Non-Framed Access.
<?rfc needLines="43"?>
<figure align="center" suppress-title="true"><artwork><![CDATA[
+-----------+
| Command |
|-----+-----+
Attribute Name | ACR | ACA |
---------------------------------------|-----+-----+
Accounting-Auth-Method | 0-1 | 0 |
Accounting-Input-Octets | 1 | 0 |
Accounting-Output-Octets | 1 | 0 |
Accounting-Record-Type | 1 | 1 |
Accounting-Record-Number | 0-1 | 0-1 |
Accounting-Realtime-Required | 0-1 | 0-1 |
Accounting-Sub-Session-Id | 0-1 | 0-1 |
Acct-Application-Id | 0-1 | 0-1 |
Acct-Session-Id | 1 | 0-1 |
Acct-Multi-Session-Id | 0-1 | 0-1 |
Acct-Authentic | 1 | 0 |
Acct-Delay-Time | 0-1 | 0 |
Acct-Interim-Interval | 0-1 | 0-1 |
Acct-Link-Count | 0-1 | 0 |
Acct-Session-Time | 1 | 0 |
Authorization-Lifetime | 0-1 | 0 |
Callback-Id | 0-1 | 0 |
Callback-Number | 0-1 | 0 |
Called-Station-Id | 0-1 | 0 |
Calling-Station-Id | 0-1 | 0 |
Class | 0+ | 0+ |
Connection-Info | 0+ | 0 |
Destination-Host | 0-1 | 0 |
Destination-Realm | 1 | 0 |
Event-Timestamp | 0-1 | 0-1 |
Error-Message | 0 | 0-1 |
Error-Reporting-Host | 0 | 0-1 |
Failed-AVP | 0 | 0+ |
Login-IP-Host | 0+ | 0 |
Login-IPv6-Host | 0+ | 0 |
Login-LAT-Service | 0-1 | 0 |
Login-LAT-Node | 0-1 | 0 |
Login-LAT-Group | 0-1 | 0 |
Login-LAT-Port | 0-1 | 0 |
Login-Service | 0-1 | 0 |
Login-TCP-Port | 0-1 | 0 |
---------------------------------------|-----+-----+
]]></artwork></figure>
<figure align="center" suppress-title="true"><artwork><![CDATA[
+-----------+
| Command |
|-----+-----+
Attribute Name | ACR | ACA |
---------------------------------------|-----+-----+
NAS-Identifier | 0-1 | 0-1 |
NAS-IP-Address | 0-1 | 0-1 |
NAS-IPv6-Address | 0-1 | 0-1 |
NAS-Port | 0-1 | 0-1 |
NAS-Port-Id | 0-1 | 0-1 |
NAS-Port-Type | 0-1 | 0-1 |
Origin-AAA-Protocol | 0-1 | 0-1 |
Origin-Host | 1 | 1 |
Origin-Realm | 1 | 1 |
Origin-State-Id | 0-1 | 0-1 |
Originating-Line-Info | 0-1 | 0 |
Proxy-Info | 0+ | 0+ |
QoS-Filter-Rule | 0+ | 0 |
Route-Record | 0+ | 0+ |
Result-Code | 0 | 1 |
Session-Id | 1 | 1 |
Service-Type | 0-1 | 0-1 |
Termination-Cause | 0-1 | 0-1 |
User-Name | 0-1 | 0-1 |
Vendor-Specific-Application-Id | 0-1 | 0-1 |
---------------------------------------|-----+-----+
]]></artwork></figure>
</t>
</section>
</section>
</section>
<section title="IANA Considerations">
<t>
This section provides guidance to the Internet Assigned Numbers
Authority (IANA) regarding registration of values related to the
Diameter protocol, in accordance with BCP 26 <xref target="RFC5226"/>.
<vspace blankLines="1"/>
This document defines values in the namespaces that have been created
and defined in the Diameter Base <xref target="I-D.ietf-dime-rfc3588bis"/>.
The IANA Considerations
section of that document details the assignment criteria. Values
assigned in this document, or by future IANA action, must be
coordinated within this shared namespace.
</t>
<section title="Command Codes">
<t>
This specification assigns the value 265 from the Command Code
namespace defined in <xref target="I-D.ietf-dime-rfc3588bis"/>.
See Sections 3.1 and 3.2 for the assignment of the namespace in this specification.
</t>
</section>
<section title="AVP Codes">
<t>
This specification assigns the values 363 - 366 and 400 - 408 from
the AVP Code namespace defined in <xref target="I-D.ietf-dime-rfc3588bis"/>.
See <xref target="D-N-A-AVPs"/>
for the assignment of the namespace in this specification. Note that the
values 363 - 366 are jointly, but consistently, assigned in <xref target="RFC4004"/>.
This document also creates one new namespace to be
managed by IANA, as described in <xref target="A-A-M-A-V"/>
<vspace blankLines="1"/>
This specification also specifies the use of AVPs in the 0 - 255
range, which are listed in <xref target="RADIUSTypes"/>
These values are assigned according to the policy stated in
<xref target="RFC2865">Section 6 of</xref>,
<xref target="RFC3575">as amended by</xref>.
</t>
</section>
<section title="Application Identifier">
<t>
This specification uses the value one (1) in the Application
Identifier namespace as assigned in <xref target="I-D.ietf-dime-rfc3588bis"/>.
See <xref target="A-A-S"/> above for more information.
</t>
</section>
<section title="CHAP-Algorithm AVP Values">
<t>
As defined in <xref target="C-AUTH-AVP"/>,
the CHAP-Algorithm AVP (AVP Code 403) uses
the values of the "PPP AUTHENTICATION ALGORITHMS" namespace defined
in <xref target="RFC1994"/>.
</t>
</section>
<section title="Accounting-Auth-Method AVP Values" anchor="A-A-M-A-V">
<t>
As defined in <xref target="A-A-M-AVP"/>
the Accounting-Auth-Method AVP (AVP Code 406) defines the values 1 - 5.
All remaining values are available for assignment via the IETF Review policy
<xref target="RFC5226"/>.
</t>
</section>
</section>
<section title="Security Considerations">
<t>
This document describes the extension of Diameter for the NAS
application. The security considerations of the Diameter protocol
itself have been discussed in <xref target="I-D.ietf-dime-rfc3588bis"/>.
Use of this application of
Diameter MUST take into consideration the security issues and
requirements of the Base protocol.
<vspace blankLines="1"/>
This document does not contain a security protocol but does discuss
how PPP authentication protocols can be carried within the Diameter
protocol. The PPP authentication protocols described are PAP and
CHAP.
<vspace blankLines="1"/>
The use of PAP SHOULD be discouraged, as it exposes users' passwords
to possibly non-trusted entities. However, PAP is also frequently
used for use with One-Time Passwords, which do not expose a security risk.
<vspace blankLines="1"/>
This document also describes how CHAP can be carried within the
Diameter protocol, which is required for RADIUS backward
compatibility. The CHAP protocol, as used in a RADIUS environment,
facilitates authentication replay attacks.
<vspace blankLines="1"/>
The use of the EAP authentication protocols <xref target="RFC4072"/>
can offer better security, given a method suitable for the circumstances.
</t>
</section>
</middle>
<back>
<references title="Normative References">
&I-D.ietf-dime-rfc3588bis;
&rfc3539;
&rfc2865;
<reference anchor="RADIUSTypes" target="http://www.iana.org/assignments/radius-types">
<front>
<title>RADIUS Types</title>
<author>
<organization>IANA</organization>
</author>
<date></date>
</front>
</reference>
&rfc3162;
&rfc3516;
&rfc1994;
&rfc5226;
&rfc2119;
<reference anchor="ANITypes" target="http://www.nanpa.com/number_resource_info/ani_ii_assignments.html">
<front>
<title>ANI Assignments</title>
<author>
<organization>NANPA Number Resource Info</organization>
</author>
<date></date>
</front>
</reference>
</references>
<references title="Informative References">
&rfc2866;
&rfc2548;
&rfc2869;
&rfc2868;
&rfc2867;
&rfc3575;
&rfc2881;
&rfc3169;
&rfc2989;
&rfc4072;
&rfc4004;
&rfc3580;
<reference anchor="AppleTalk">
<front>
<title>Inside AppleTalk</title>
<author surname="Sidhu" fullname="Gursharan Sidhu" initials="G."/>
<author surname="Andrews" fullname="Richard F. Andrews" initials="R.F."/>
<author fullname="Alan B. Oppenheimer" initials="A.B." surname="Oppenheimer"/>
<date year="1990"/>
</front>
<seriesInfo name="Second Edition" value="Apple Computer"/>
</reference>
<reference anchor="ARAP">
<front>
<title>Apple Remote Access Protocol (ARAP) Version 2.0 External Reference Specification</title>
<author>
<organization>Apple Computer</organization>
</author>
<date month="September" year="1994"/>
</front>
<seriesInfo name="R0612LL/B" value=""/>
</reference>
<reference anchor="IPX">
<front>
<title>NetWare System Technical Interface Overview</title>
<author>
<organization>Novell, Inc.</organization>
</author>
<date month="June" year="1989"/>
</front>
<seriesInfo name="" value="#883-000780-001"/>
</reference>
<reference anchor="LAT">
<front>
<title>Local Area Transport (LAT) Specification V5.0</title>
<author>
<organization>Digital Equipment Corp.</organization>
</author>
<date month="June" year="1989"/>
</front>
<seriesInfo name="" value="AA-NL26A-TE"/>
</reference>
&rfc2474;
&rfc2597;
&rfc3246;
<reference anchor="ISO.8859-1.1987">
<front>
<title>Information technology - 8-bit single byte coded graphic - character sets - Part 1: Latin alphabet No. 1, JTC1/SC2</title>
<author>
<organization>International Organization for Standardization</organization>
</author>
<date month="" year="1987" />
</front>
<seriesInfo name="ISO" value="Standard 8859-1" />
</reference>
&rfc1661;
&rfc1334;
&rfc2661;
&rfc1990;
&rfc2637;
</references>
<section title="Acknowledgements">
<section title="RFC 4005">
<t>
The authors would like to thank Carl Rigney, Allan C. Rubens, William
Allen Simpson, and Steve Willens for their work on the original RADIUS protocol,
from which many of the concepts in this
specification were derived. Thanks, also, to Carl Rigney for
<xref target="RFC2866"/>
and <xref target="RFC2869"/>;
Ward Willats for <xref target="RFC2869"/>;
Glen Zorn, Bernard Aboba, and Dave Mitton for <xref target="RFC2867"/>
and <xref target="RFC3162"/>;
and Dory Leifer, John Shriver, Matt Holdrege, Allan Rubens, Glen Zorn and
Ignacio Goyret for their work on <xref target="RFC2868"/>.
This document stole text and concepts from both <xref target="RFC2868"/>
and <xref target="RFC2869"/>.
Thanks go to Carl Williams for providing IPv6-specific text.
<vspace blankLines="1"/>
The authors would also like to acknowledge the following people for
their contributions in the development of the Diameter protocol:
Bernard Aboba, Jari Arkko, William Bulley, Kuntal Chowdhury, Daniel
C. Fox, Lol Grant, Nancy Greene, Jeff Hagg, Peter Heitman, Paul
Krumviede, Fergal Ladley, Ryan Moats, Victor Muslin, Kenneth Peirce,
Sumit Vakil, John R. Vollbrecht, and Jeff Weisberg.
<vspace blankLines="1"/>
Finally, Pat Calhoun would like to thank Sun Microsystems, as most of
the effort put into this document was done while he was in their employ.
</t>
</section>
<section title="RFC 4005bis">
<t>
The vast majority of the text in this document was lifted directly fro RFC 4005;
the editor owes a debt of gratitude to the authors thereof (especially Dave Mitton, who
somehow managed to make nroff paginate the AVP Occurance Tables correctly!).
</t>
</section>
</section>
</back>
</rfc>
| PAFTECH AB 2003-2026 | 2026-04-23 07:46:14 |