One document matched: draft-yeh-radext-ext-traffic-statistics-03.xml
<?xml version="1.0" encoding="US-ASCII"?>
<!-- This template is for creating an Internet Draft using xml2rfc, which is available here: http://xml.resource.org. -->
<!DOCTYPE rfc SYSTEM "rfc2629.dtd" [
<!ENTITY RFC2119 SYSTEM "http://xml.resource.org/public/rfc/bibxml/reference.RFC.2119.xml">
<!ENTITY RFC2474 SYSTEM "http://xml.resource.org/public/rfc/bibxml/reference.RFC.2474.xml">
<!ENTITY RFC2865 SYSTEM "http://xml.resource.org/public/rfc/bibxml/reference.RFC.2865.xml">
<!ENTITY RFC2866 SYSTEM "http://xml.resource.org/public/rfc/bibxml/reference.RFC.2866.xml">
<!ENTITY RFC2869 SYSTEM "http://xml.resource.org/public/rfc/bibxml/reference.RFC.2869.xml">
<!ENTITY RFC3162 SYSTEM "http://xml.resource.org/public/rfc/bibxml/reference.RFC.3162.xml">
<!ENTITY RFC3575 SYSTEM "http://xml.resource.org/public/rfc/bibxml/reference.RFC.3575.xml">
<!ENTITY RFC4818 SYSTEM "http://xml.resource.org/public/rfc/bibxml/reference.RFC.4818.xml">
<!ENTITY RFC5226 SYSTEM "http://xml.resource.org/public/rfc/bibxml/reference.RFC.5226.xml">
<!ENTITY RFC6158 SYSTEM "http://xml.resource.org/public/rfc/bibxml/reference.RFC.6158.xml">
]>
<?xml-stylesheet type='text/xsl' href='rfc2629.xslt'?>
<!-- used by XSLT processors -->
<!-- For a complete list and description of processing instructions (PIs), please see ttp://xml.resource.org/authoring/README.html. -->
<?rfc strict="yes"?>
<!-- give errors regarding ID-nits and DTD validation -->
<!-- control the table of contents (ToC) -->
<?rfc toc="yes"?>
<!-- generate a ToC -->
<?rfc tocdepth="4"?>
<!-- the number of levels of subsections in ToC. default: 3 -->
<!-- control references -->
<?rfc symrefs="yes"?>
<!-- use symbolic references tags, i.e, [RFC2119] instead of [1] -->
<?rfc sortrefs="yes" ?>
<!-- sort the reference entries alphabetically -->
<!-- control vertical white space (using these PIs as follows is recommended by the RFC Editor) -->
<?rfc compact="yes" ?>
<!-- do not start each main section on a new page -->
<?rfc subcompact="no" ?>
<!-- keep one blank line between list items -->
<!-- end of list of popular I-D processing instructions -->
<rfc category="std" docName="draft-yeh-radext-ext-traffic-statistics-03" ipr="trust200902">
<!-- category values: std, bcp, info, exp, and historic ipr values: trust200902, noModificationTrust200902, noDerivativesTrust200902, or pre5378Trust200902 you can add the attributes updates="NNNN" and obsoletes="NNNN" they will automatically be output with "(if approved)" -->
<!-- ***** FRONT MATTER ***** -->
<front>
<!-- The abbreviated title is used in the page header - it is only necessary if the full title is longer than 39 characters -->
<title abbrev="RADIUS Accounting Extensions"> RADIUS Accounting Extensions for Traffic Statistics</title>
<author fullname="Leaf Y. Yeh" initials="L." surname="Yeh">
<organization>Huawei Technologies</organization>
<address>
<postal>
<street></street>
<city></city>
<region>Shenzhen</region>
<code></code>
<country>P. R. China</country>
</postal>
<email>leaf.y.yeh@huawei.com</email>
</address>
</author>
<date year="2012" />
<!-- Meta-data Declarations -->
<area>Ops&Mgmt</area>
<workgroup>Radext Working Group</workgroup>
<keyword>RADIUS Attributes</keyword>
<keyword>Dual Stack</keyword>
<keyword>Traffic Statistics</keyword>
<abstract>
<t>This document specifies the RADIUS extensions of attributes for the traffic statistics with different type, which can be used to support the differentiated accounting policies and traffic recording on the AAA server.</t>
</abstract>
</front>
<!-- ***** MIDDLE MATTER ***** -->
<middle>
<section anchor="s1" title="Introduction">
<t>RADIUS has been widely used as the centralized authentication, authorization and user management method for the service provision in Broadband access network. <xref target="RFC3162"/>, <xref target="RFC4818"/> and <xref target="ietf-radext-ipv6-access-09"/> has specified some attributes to support the service provision for IPv6 access. In the meantime, Radius is also a protocol for carrying accounting information between a Network Access Server and a shared accounting server. In the scenarios of dual-stack or any other IPv6 transition use case, there is a demand to report the separated IPv4 & IPv6 traffic statistics for the differential accounting and traffic recording.</t>
<t><xref target="BBF TR-187"/>, whose purpose is to describe the network architecture and elements requirements in the PPPoE scenario to support IPv6-only or dual-stack for Internet access service, explicitly expressed this demand in its section 9.4, that the BNG must also be able to support separate queues, input and output counters for IPv4 or IPv6 traffic. And it recommended to use the Radius attributes of Acct-Input-Octets (42), Acct-Output-Octets (43), Acct-Input-Packets (47), Acct-Output-Packets (48) for the combination of IPv6 and IPv4 traffic. Note that BNG of BBF is a kind of broadband NAS of IETF. The new RADIUS attributes for reporting the separated IPv4 or IPv6 traffic statistics are required.</t>
<t><xref target="draft-hu-v6ops-radius-issues-ipv6-00"/> presented the same issue on 'protocol specific accounting' for the dual-stack traffic statistics, but it also limits to the PPP case. <xref target="draft-maglione-radext-ipv6-acct-extensions-01"/> and <xref target="draft-yeh-radext-dual-stack-access-02"/> tried to defined a batch of attributes on the traffic statistics respectively for the IPv6-only access and dual-stack access in the traditional type space with the flat mode , while <xref target="draft-winter-radext-fancyaccounting-00"/> indicated that the accounting attributes of Input-Octets, Output-Octets, Input-Packets and Output-Packets can be grouped in the new basic data type of TLV-nesting defined in the section 2.3 of <xref target="draft-ietf-radext-radius-extensions-06"/> for the extended type space. According to <xref target="RFC6158"/> and the section 6.3 of <xref target="draft-ietf-radext-radius-extensions-06"/>, Nesting-TLV is the only recommendation for the new attribute design now, which intends to employ multiple fields in the complex data type. Based on the judge of the quickly-exhausted traditional type space, the Radext Working Group tends to adopt the new data type of nesting-TLV defined for the extended type space to report the traffic statistics for the accounting extension.</t>
</section>
<section anchor="s2" title="Terminology and Conventions">
<t>This document describes some new RADIUS attributes and the associated usage on NAS and AAA server. This document should be read in conjunction with the relevant RADIUS specifications, including <xref target="RFC2865"/>, <xref target="RFC2866"/>, <xref target="RFC2869"/>, and <xref target="draft-ietf-radext-radius-extensions-06"/>, for a complete mechanism. Definitions for terms and acronyms not specifically defined in this document are defined in <xref target="RFC2865"/>, <xref target="RFC2866"/>, <xref target="RFC2869"/>, <xref target="RFC3575"/>, <xref target="RFC6158"/>, and <xref target="draft-ietf-radext-radius-extensions-06"/>.</t>
<t>The keywords MUST, MUST NOT, REQUIRED, SHALL, SHALL NOT, SHOULD, SHOULD NOT, RECOMMENDED, MAY, and OPTIONAL, when they appear in this document, are to be interpreted as described in BCP 14, <xref target="RFC2119"/>.</t>
</section>
<section anchor="s3" title="Deployment Scenarios">
<t>Figure 1 show the typical use case of the traffic statistics reporting for the dual-stack users.</t>
<figure anchor="f1" title="Traffic Statistics of Dual-Stack Users for RADIUS Accounting">
<artwork>
+----------+ +----------+ +----------+
| Host / | PPPoE | | RADIUS | AAA |
| Customer | ------------ | NAS | ------------ | Server |
| Router | IPoE | | Accounting | |
+----------+ +----------+ +----------+
Dual-Stack Separated queues and counter
for IPv4 and IPv6 traffic
</artwork>
</figure>
<t>Note that traffic statistics reporting is also needed in the IPv6 transition cases, such as DS-Lite, 6rd or the potential MAP, where AFTR (Address Family Transition Router) or BR (Border Router) acts as the broadband NAS.</t>
</section>
<section anchor="s4" title="Acct-Traffic-Statistics attribute">
<t>The attribute of Acct-traffic-statistics is designed according to the guidelines described in <xref target="RFC6158"/> and section 6 of <xref target="draft-ietf-radext-radius-extensions-06"/>. It adopts the data structure of the TLV nesting, has 1 container attribute, Acct-Traffic-Statistics, and 6 contained sub-attributes, Stack-Type, Input-Octets, Output-Octets, Input-Packets, Output-Packets, DSCP-Type (Differentiated Services CodePoint) to support the extensible types of traffic statistics. The sub-attribute of Stack-Type must be included in the container attribute; one or more of Input-Octets, Output-Octets, Input-Packets or Output-Packets sub-attributes much be also included; while the sub-attribute of DSCP-Type is optional for the detailed specified traffic type in the container attribute. Because each of the sub-attributes has its own type code, the appearance of the contained sub-attributes is not necessary in a fixed order.</t>
<section anchor="s4.1" title="Container attribute of Acct-Traffic-Statistics">
<t>Description
<list style="empty">
<t>The container attribute of Acct-Traffic-Statistics, which includes sub-attributes of Stack-Type, or DSCP-Type, and Input-Octets, Output-Octets, Input-Packets or Output-Packets, reports how many octets or packets of the specified traffic type, from the user or sent to the user, from the starting of the associated service provided. The sub-attributes of Stack-Type or DSCP-Type indicates the specified traffic type. Acct-traffic-statistics can be presented in Accounting-Request(4) message while the Acct-Status-Type(40) is set to Interim-Update or Stop.</t>
<t>A summary of the Acct-Traffic-Statistics attribute format is shown as below. The fields are transmitted from left to right.</t>
</list></t>
<figure><artwork>
0 1 2 3
0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Type | Length | Extended-Type | Value |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Value (cont.)...
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
</artwork></figure>
<t>Type
<list style="empty">
<t>241, which indicates the extended type space.</t>
</list></t>
<t>Length
<list style="empty">
<t>The length of the whole attribute in octet.</t>
</list></t>
<t>Extended-Type
<list style="empty">
<t>TBA for Acct-Traffic-Statistics (by IANA)</t>
</list></t>
<t>Value
<list style="empty">
<t>The Value of the container attribute are the sub-attributes defined in section 4.2 in TLV nesting mode. At least the sub-attribute of Stack-Type, and one of Input-Octets, Output-Octets, Input-Packets or Output-Packets sub-attributes must be included.</t>
</list></t>
</section>
<section anchor="s4.2" title="Contained attribute of Acct-Traffic-Statistics">
<section anchor="s4.2.1" title="Acct-Traffic-Statistics.Stack-Type">
<t>Description
<list style="empty">
<t>The sub-attribute of Acct-Traffic-Statistics.Stack-Type indicates the type of the separated and combined traffic of IPv4 and IPv6.</t>
<t>A summary of the Acct-Traffic-Statistics.Stack-Type attribute format is shown as below. The fields are transmitted from left to right.</t>
</list></t>
<figure><artwork>
0 1 2 3
0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Type | Length | Value |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Value (cont.) |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
</artwork></figure>
<t>Type
<list style="empty">
<t>TBA.1 for Acct-Traffic-Statistics.Stack-Type (by IANA)</t>
</list></t>
<t>Length
<list style="empty">
<t>6</t>
</list></t>
<t>Value
<list style="empty">
<t>Enumerated Data Type in 4-Octet unsigned integer defined in <xref target="RFC6158"/>. The beginning 3 Octets are reserved for future use, and are set to 0x00 now. The decimal value of the last octet is defined as follows:</t>
<t>0 the combined traffic of IPv4 and IPv6</t>
<t>1 the separated traffic of IPv4</t>
<t>2 the separated traffic of IPv6</t>
</list></t>
</section>
<section anchor="s4.2.2" title="Acct-Traffic-Statistics.Input-Octets">
<t>Description
<list style="empty">
<t>This attribute indicates how many octets in IP layer have been received from the user from the starting of the service authorized. Note that IP layer is explicit here because this accounting attribute is definitely related to the IP service.</t>
<t>A summary of the Acct-Traffic-Statistics.Input-Octets attribute format is shown as below. The fields are transmitted from left to right.</t>
</list></t>
<figure><artwork>
0 1 2 3
0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Type | Length | Value |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Value (cont.) |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Value (cont.) |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
</artwork></figure>
<t>Type
<list style="empty">
<t>TBA.2 for Acct-Traffic-Statistics.Input-Octets (by IANA)</t>
</list></t>
<t>Length
<list style="empty">
<t>10</t>
</list></t>
<t>Value
<list style="empty">
<t>Integer64 data type in 8-Octet unsigned integer defined in <xref target="draft-ietf-radext-radius-extensions-06"/>.</t>
</list></t>
</section>
<section anchor="s4.2.3" title="Acct-Traffic-Statistics.Output-Octets">
<t>Description
<list style="empty">
<t>This attribute indicates how many octets in IP layer sent to the user from the starting of the service authorized.</t>
<t>A summary of the Acct-Traffic-Statistics.Output-Octets attribute format is shown as below. The fields are transmitted from left to right.</t>
</list></t>
<figure><artwork>
0 1 2 3
0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Type | Length | Value |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Value (cont.) |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Value (cont.) |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
</artwork></figure>
<t>Type
<list style="empty">
<t>TBA.3 for Acct-Traffic-Statistics.Output-Octets (by IANA)</t>
</list></t>
<t>Length
<list style="empty">
<t>10</t>
</list></t>
<t>Value
<list style="empty">
<t>Integer64 data type in 8-Octet unsigned integer defined in <xref target="draft-ietf-radext-radius-extensions-06"/>.</t>
</list></t>
</section>
<section anchor="s4.2.4" title="Acct-Traffic-Statistics.Input-Packets">
<t>Description
<list style="empty">
<t>This attribute indicates how many packets in IP layer received from the user from the starting of the service authorized.</t>
<t>A summary of the Acct-Traffic-Statistics.Input-Packets attribute format is shown as below. The fields are transmitted from left to right.</t>
</list></t>
<figure><artwork>
0 1 2 3
0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Type | Length | Value |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Value (cont.) |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Value (cont.) |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
</artwork></figure>
<t>Type
<list style="empty">
<t>TBA.4 for Acct-Traffic-Statistics.Input-Packets (by IANA)</t>
</list></t>
<t>Length
<list style="empty">
<t>10</t>
</list></t>
<t>Value
<list style="empty">
<t>Integer64 data type in 8-Octet unsigned integer defined in <xref target="draft-ietf-radext-radius-extensions-06"/>.</t>
</list></t>
</section>
<section anchor="s4.2.5" title="Acct-Traffic-Statistics.Output-Packets">
<t>Description
<list style="empty">
<t>This attribute indicates how many packets in IP layer sent to the user from the starting of the service authorized.</t>
<t>A summary of the Acct-Traffic-Statistics.Output-Packets attribute format is shown as below. The fields are transmitted from left to right.</t>
</list></t>
<figure><artwork>
0 1 2 3
0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Type | Length | Value |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Value (cont.) |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Value (cont.) |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
</artwork></figure>
<t>Type
<list style="empty">
<t>TBA.5 for Acct-Traffic-Statistics.Output-Packets (by IANA)</t>
</list></t>
<t>Length
<list style="empty">
<t>10</t>
</list></t>
<t>Value
<list style="empty">
<t>Integer64 data type in 8-Octet unsigned integer defined in <xref target="draft-ietf-radext-radius-extensions-06"/>.</t>
</list></t>
</section>
<section anchor="s4.2.6" title="Acct-Traffic-Statistics.DSCP-Type">
<t>Description
<list style="empty">
<t>The sub-attribute of Acct-Traffic-Statistics.DSCP-Type indicates the DSCP type of the separated or combined IPv4 and IPv6 traffic.</t>
<t>A summary of the Acct-Traffic-Statistics.DSCP-Type attribute format is shown as below. The fields are transmitted from left to right.</t>
</list></t>
<figure><artwork>
0 1 2 3
0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Type | Length | Value |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Value (cont.) |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
</artwork></figure>
<t>Type
<list style="empty">
<t>TBA.6 for Acct-Traffic-Statistics.DSCP-Type (by IANA)</t>
</list></t>
<t>Length
<list style="empty">
<t>6</t>
</list></t>
<t>Value
<list style="empty">
<t>Enumerated Data Type in 4-Octet unsigned integer defined in <xref target="RFC6158"/>. The beginning 3 Octets are reserved for future use, and are set to 0x00 now. The last 6 bits of the last octet is used to contain the DSCP value as per <xref target="RFC2474"/></t>
</list></t>
</section>
</section>
</section>
<section anchor="s5" title="Table of Attribute">
<t>The following table provides a guide to which attributes may be found in which kinds of packets, and in what quantity.</t>
<figure><artwork>
Req- Acc- Rej- Chall Accounting # Attribute
uest ept ect -enge Request
0 0 0 0 0-1 TBA Acct-Traffic-Statistics
</artwork></figure>
<t>The meaning of the above table entries is as follows:</t>
<figure><artwork>
0 This attribute MUST NOT be present.
0+ Zero or more instances of this attribute MAY be present.
0-1 Zero or one instance of this attribute MAY be present.
1 Exactly one instance of this attribute MUST be present.
1+ One or more of these attributes MUST be present.
</artwork></figure>
</section>
<section anchor="s6" title="Diameter Considerations">
<t>Given that the Attributes defined in this document are allocated from the RADIUS extended type space, no special handling is required by Diameter entities.</t>
</section>
<section anchor="s7" title="Security Considerations">
<t>Known security vulnerabilities of the RADIUS protocol may apply to its attributes. Security issues related RADIUS are described in section 8 of <xref target="RFC2865"/>, section 5 of <xref target="RFC3162"/>.</t>
</section>
<section anchor="s8" title="IANA Considerations">
<t>The authors of this document request to assign new Radius type codes for Acct-Traffic-Statistics and its following sub-attributes.</t>
<figure><artwork>
Acct-Traffic-Statistics.Stack-Type
Acct-Traffic-Statistics.Input-Octets
Acct-Traffic-Statistics.Output-Octets
Acct-Traffic-Statistics.Input-Packets
Acct-Traffic-Statistics.Output-Packets
Acct-Traffic-Statistics.DSCP-Type
</artwork></figure>
<t>These type codes should be allocated from the RADIUS extended type space based on section 10 of <xref target="draft-ietf-radext-radius-extensions-06"/> and "IETF Review" policy <xref target="RFC5226"/>.</t>
</section>
<section anchor="s9" title="Acknowledgements">
<t>Thanks to Roberta Maglione, Jie Hu for their efforts in the history to bring this problem to IETF, Stefan Winter for his effort to introduce TLV in the attribute design, and Alan DeKok, Peter Deacon for their valuable comments in the mailing list of Radext.</t>
</section>
</middle>
<!-- ***** BACK MATTER ***** -->
<back>
<references title="Normative References">
&RFC2119;
&RFC2474;
&RFC2865;
&RFC2866;
&RFC2869;
&RFC3162;
&RFC3575;
&RFC4818;
&RFC5226;
<reference anchor='draft-ietf-radext-radius-extensions-06'>
<front>
<title>Remote Authentication Dial In User Service (RADIUS) Protocol Extensions</title>
<author initials='A.' surname='DeKok' fullname='Alan DeKok' />
<author initials='A.' surname='Lior' fullname='Avi Lior' />
<date year='2012' month='Apr.' />
</front>
</reference>
</references>
<references title="Informative References">
&RFC6158;
<reference anchor='BBF TR-187'>
<front>
<title>IPv6 for PPP Broadband Access, Issue 1</title>
<author initials='' surname='Broadband Forum' fullname='' />
<date year='2010' month='May' />
</front>
</reference>
<reference anchor='ietf-radext-ipv6-access-09'>
<front>
<title>RADIUS attributes for IPv6 Access Networks</title>
<author initials='B.' surname='Lourdelet' fullname='Benoit Lourdelet' />
<author initials='W.' surname='Dec' fullname='Wojciech Dec' />
<author initials='B.' surname='Sarikaya' fullname='Behcet Sarikaya' />
<author initials='G.' surname='Zorn' fullname='Glen Zorn' />
<author initials='D.' surname='Miles' fullname='David Miles' />
<date year='2012' month='May' />
</front>
</reference>
<reference anchor='draft-hu-v6ops-radius-issues-ipv6-00'>
<front>
<title>RADIUS issues in IPv6 deployments</title>
<author initials='J.' surname='Hu' fullname='Jie Hu' />
<author initials='L.' surname='Yan' fullname='Lu Yan' />
<author initials='Q.' surname='Wang' fullname='Qian Wang' />
<author initials='J.' surname='Qin' fullname='Jacni Qin' />
<date year='2011' month='February' />
</front>
</reference>
<reference anchor='draft-maglione-radext-ipv6-acct-extensions-01'>
<front>
<title>RADIUS Accounting Extensions for IPv6</title>
<author initials='R.' surname='Maglione' fullname='Roberta Maglione' />
<author initials='S.' surname='Krishnan' fullname='Suresh Krishnan' />
<author initials='A.' surname='Kavanagh' fullname='Alan Kavanagh' />
<author initials='B.' surname='Varga' fullname='Balazs Varga' />
<author initials='J.' surname='Kaippallimalil' fullname='John Kaippallimalil' />
<date year='2011' month='January' />
</front>
</reference>
<reference anchor='draft-winter-radext-fancyaccounting-00'>
<front>
<title>RADIUS Accounting for traffic classes</title>
<author initials='S.' surname='Winter' fullname='Stefan Winter' />
<date year='2011' month='March' />
</front>
</reference>
<reference anchor='draft-yeh-radext-dual-stack-access-02'>
<front>
<title>RADIUS Attributes for Dual Stack Access</title>
<author initials='L.' surname='Yeh' fullname='Leaf Yeh' />
<author initials='T.' surname='Tsou' fullname='Tina Tsou' />
<date year='2011' month='March' />
</front>
</reference>
</references>
</back>
</rfc>
| PAFTECH AB 2003-2026 | 2026-04-24 04:21:51 |