| Network Working Group | D. Cheng |
| Internet-Draft | Huawei |
| Intended status: Standards Track | J. Korhonen |
| Expires: April 21, 2016 | Broadcom Corporation |
| M. Boucadair | |
| France Telecom | |
| S. Sivakumar | |
| Cisco Systems | |
| October 19, 2015 |
RADIUS Extensions for IP Port Configuration and Reporting
draft-ietf-radext-ip-port-radius-ext-06
This document defines three new RADIUS attributes. For devices that implementing IP port ranges, these attributes are used to communicate with a RADIUS server in order to configure and report TCP/UDP ports and ICMP identifiers, as well as mapping behavior for specific hosts. This mechanism can be used in various deployment scenarios such as CGN (Carrier Grade NAT), NAT64, Provider WLAN Gateway, etc.
The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this document are to be interpreted as described in RFC 2119 [RFC2119].
This Internet-Draft is submitted in full conformance with the provisions of BCP 78 and BCP 79.
Internet-Drafts are working documents of the Internet Engineering Task Force (IETF). Note that other groups may also distribute working documents as Internet-Drafts. The list of current Internet-Drafts is at http://datatracker.ietf.org/drafts/current/.
Internet-Drafts are draft documents valid for a maximum of six months and may be updated, replaced, or obsoleted by other documents at any time. It is inappropriate to use Internet-Drafts as reference material or to cite them other than as "work in progress."
This Internet-Draft will expire on April 21, 2016.
Copyright (c) 2015 IETF Trust and the persons identified as the document authors. All rights reserved.
This document is subject to BCP 78 and the IETF Trust's Legal Provisions Relating to IETF Documents (http://trustee.ietf.org/license-info) in effect on the date of publication of this document. Please review these documents carefully, as they describe your rights and restrictions with respect to this document. Code Components extracted from this document must include Simplified BSD License text as described in Section 4.e of the Trust Legal Provisions and are provided without warranty as described in the Simplified BSD License.
In a broadband network, customer information is usually stored on a RADIUS server [RFC2865] and at the time when a user initiates an IP connection request, the RADIUS server will populate the user's configuration information to the Network Access Server (NAS), which is usually co-located with the Border Network Gateway (BNG), after the connection request is granted. The Carrier Grade NAT (CGN) function may also be implemented on the BNG, and therefore the CGN TCP/UDP port (or ICMP identifier) mapping(s) behavior(s) can be configured on the RADIUS server as part of the user profile, and populated to the NAS in the same manner. In addition, during the operation, the CGN can also convey port/identifier mapping behavior specific to a user to the RADIUS server, as part of the normal RADIUS accounting process.
The CGN device that communicates with a RADIUS server using RADIUS extensions defined in this document may perform NAT44 [RFC3022], NAT64 [RFC6146], or Dual-Stack Lite AFTR [RFC6333] function.
For the CGN case, when IP packets traverse a CGN device, it would perform TCP/UDP source port mapping or ICMP identifier mapping as required. A TCP/ UDP source port or ICMP identifier, along with source IP address, destination IP address, destination port and protocol identifier if applicable, uniquely identify a session. Since the number space of TCP/UDP ports and ICMP identifiers in CGN's external realm is shared among multiple users assigned with the same IPv4 address, the total number of a user's simultaneous IP sessions is likely to be subject to port quota (see Section 5 of [RFC6269]).
The attributes defined in this document may also be used to report the assigned port range in some deployments such as Provider WLAN [I-D.gundavelli-v6ops-community-wifi-svcs]. For example, a visiting host can be managed by a CPE (Customer Premises Equipment ) which will need to report the assigned port range to the service platform. This is required for identification purposes (see TR-146 [TR-146] for example).
This document proposes three new attributes as RADIUS protocol's extensions, and they are used for separate purposes as follows:
This document leverages the protocol defined in [RFC7012] by proposing a mapping between type field of RADIUS TLV and Element ID of IPFIX. It also proposes a few new IPFIX Elements as required by this document (see Section 3).
This document was constructed using the [RFC2629].
This document makes use if the following terms:
Note the terms "internal IP address", "internal port", "internal realm", "external IP address", "external port", "external realm", and "mapping" and their semantics are the same as in [RFC6887], and [RFC6888].
These three new attributes are defined in the following sub-sections:
All these attributes are allocated from the RADIUS "Extended Type" code space per [RFC6929].
This attribute is RADIUS Extended-Type, and contains a set of embedded TLVs defined in Section 3.2.1 (IP-Port-Type TLV), Section 3.2.2 (IP-Port-Limit TLV), and Section 3.2.3 (IP-Port-Ext-IPv4-Addr TLV). It specifies the maximum number of IP ports as indicated in IP-Port-Limit TLV, of a specific port type as indicated in IP-Port-Type TLV, and associated with a given IPv4 address as indicated in IP-Port-Ext-IPv4-Addr TLV for an end user.
Note that when IP-Port-Ext-IPv4-Addr TLV is not included as part of the IP-Port-Limit Attribute, the port limit is applied to all the IPv4 addresses managed by the port device, e.g., a CGN or NAT64 device.
The IP-Port-Limit Attribute MAY appear in an Access-Accept packet. It MAY also appear in an Access-Request packet as a hint by the device supporting port ranges, which is co-allocated with the NAS, to the RADIUS server as a preference, although the server is not required to honor such a hint.
The IP-Port-Limit Attribute MAY appear in a CoA-Request packet.
The IP-Port-Limit Attribute MAY appear in an Accounting-Request packet.
The IP-Port-Limit Attribute MUST NOT appear in any other RADIUS packets.
The format of the IP-Port-Limit Attribute is shown in Figure 1. The fields are transmitted from left to right.
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 ...
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Figure 1
Type:
Length:
Extended-Type:
Value:
IP-Port-Limit attribute is associated with the following identifier: Type(TBA1).Extended-Type(TBA2).[IP-Port-Limit TLV (TBA6),IP-Port-Type TLV(TBA5), {IP-Port-Ext-IPv4-Addr TLV(TBA7)}].
This attribute is RADIUS Extended-Type, and contains a set of embedded TLVs defined in Section 3.2.1(IP-Port-Type TLV), Section 3.2.9(IP-Port-Range-Start TLV), Section 3.2.10 (IP-Port-Range-End TLV), Section 3.2.8 (IP-Port-Alloc TLV), Section 3.2.3 (IP-Port-Ext-IPv4-Addr TLV), and Section 3.2.11 (IP-Port-Local-Id TLV).
This attribute contains a range of contiguous IP ports of a specific port type and associated with an IPv4 address that are either allocated or deallocated by a device for a given subscriber, and the information is intended to send to RADIUS server.
This attribute can be used to convey a single IP port number; in such case IP-Port-Range-Start and IP-Port-Range-End conveys the same value.
Within an IP-Port-Range Attribute, the IP-Port-Alloc TLV is always included. For port allocation, both IP-Port-Range-Start TLV and IP-Port-Range-End TLV must be included; for port deallocation, the inclusion of these two TLVs is optional and if not included, it implies that all ports that are previously allocated are now deallocated. Both IP-Port-Ext-IPv4-Addr TLV and IP-Port-Local-Id TLV are optional and if included, they are used by a port device (e.g., a CGN device) to identify the end user.
The IP-Port-Range Attribute MAY appear in an Accounting-Request packet.
The IP-Port-Range Attribute MUST NOT appear in any other RADIUS packets.
The format of the IP-Port-Range Attribute format is shown in Figure 2. The fields are transmitted from left to right.
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 ... +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Figure 2
Type:
Length:
Extended-Type:
Value:
The IP-Port-Range attribute is associated with the following identifier: Type(TBA1).Extended-Type(TBA3).[IP-Port-Alloc TLV (TBA12), IP-Port-Type TLV(TBA5), {IP-Port-Range-Start TLV(TBA13), IP-Port-Range-End TLV(TBA14)}, {IP-Port-Ext-IPv4-Addr TLV (TBA7)}, {IP-Port-Local-Id TLV (TBA15)}].
This attribute is RADIUS Extended-Type, and contains a set of embedded TLVs defined in Section 3.2.1(IP-Port-Type TLV), Section 3.2.6(IP-Port-Int-Port TLV), Section 3.2.7(IP-Port-Ext-Port TLV), Section 3.2.4(IP-Port-Int-IPv4-Addr TLV) or Section 3.2.5(IP-Port-Int-IPv6-Addr TLV), Section 3.2.11(IP-Port-Local-Id TLV) and Section 3.2.3 (IP-Port-Ext-IP-Addr TLV).
The attribute contains a 2-byte IP internal port number that is associated with an internal IPv4 or IPv6 address, or a locally significant identifier at the customer site, and a 2-byte IP external port number that is associated with an external IPv4 address. The internal IPv4 or IPv6 address, or the local identifier must be included; the external IPv4 address may also be included.
The IP-Port-Forwarding-Map Attribute MAY appear in an Access-Accept packet. It MAY also appear in an Access-Request packet as a hint by the device supporting port mapping, which is co-allocated with the NAS, to the RADIUS server as a preference, although the server is not required to honor such a hint.
The IP-Port-Forwarding-Map Attribute MAY appear in a CoA-Request packet.
The IP-Port-Forwarding-Map Attribute MAY also appear in an Accounting-Request packet.
The attribute MUST NOT appear in any other RADIUS packet.
The format of the IP-Port-Forwarding-Map Attribute is shown in Figure 3. The fields are transmitted from left to right.
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 .... +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Figure 3
Type:
Length:
Extended-Type:
Value:
The IP-Port-Forwarding-Map attribute is associated with the following identifier: Type(TBA1).Extended-Type(TBA4). [IP-Port-Int-Port TLV(TBA10), IP-Port-Ext-Port TLV(TBA11), IP-Port-Type TLV(TBA5), {IP-Port-Int-IPv4-Addr TLV(TBA8) | IP-Port-Int-IPv6-Addr TLV(TBA9)}, {IP-Port-Ext-IPv4-Addr TLV(TBA7)}].
This TLV (Figure 4) uses the format defined in [RFC6929]. Its Type field contains a value that uniquely refers to IPFIX Element transportType (TBAx1), and its Value field contains IPFIX Element transportType, which indicates the type of IP transport type as follows:
1:
2:
3:
4:
5:
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 | transportType
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
transportType |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Figure 4
Type:
Length:
transportType:
This TLV (Figure 5) uses the format defined in [RFC6929]. Its Type field contains a value that uniquely refers to IPFIX Element natTransportLimit (TBAx2), and its Value field contains IPFIX Element natTransportLimit, which indicates the maximum number of ports of a specified IP-Port-Type and associated with a given IPv4 address assigned to a subscriber.
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 | natTransportLimit
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
natTransportLimit |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Figure 5
Type:
Length:
natTransportLimit:
This TLV (Figure 6) uses the format defined in[RFC6929]. Its Type field contains a value that uniquely refers to IPFIX Element postNATSourceIPv4Address(225), and its Value field contains IPFIX Element postNATSourceIPv4Address, which is the IPv4 source address after NAT operation (refer to [IPFIX]).
IP-Port-Ext-IPv4-Addr TLV can be included as part of the IP-Port-Limit Attribute (refer to Section 3.1.1), IP-Port-Range Attribute (refer to Section 3.1.2), and IP-Port-Forwarding-Map Attribute (refer to Section 3.1.3).
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 | postNATSourceIPv4Address
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
postNATSourceIPv4Address |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Figure 6
Type:
Length:
postNATSourceIPv4Address:
This TLV (Figure 7) uses format defined in [RFC6929]. Its Type field contains a value that uniquely refers to IPFIX Element sourceIPv4Address (8), and its Value field contains IPFIX Element sourceIPv4Address, which is the IPv4 source address before NAT operation (refer to [IPFIX]).
IP-Port-Int-IPv4-Addr TLV can be included as part of the IP-Port-Forwarding-Map Attribute (refer to Section 3.1.3).
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 | sourceIPv4Address
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
sourceIPv4Address |
+-+--+-+-+-+-+-+-++-+-+-+-+-+-+-+
Figure 7
Type:
Length:
sourceIPv4Address:
This TLV (Figure 8) uses format defined in [RFC6929]. Its Type field contains a value that uniquely refers to IPFIX Element sourceIPv6Address(27), and its Value field contains IPFIX Element sourceIPv6Address, which is the IPv6 source address before NAT operation (refer to [IPFIX]).
IP-Port-Int-IPv6-Addr TLV can be included as part of the IP-Port-Forwarding-Map Attribute (refer to Section 3.1.3).
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 | sourceIPv6Address
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
sourceIPv6Address
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
sourceIPv6Address
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
sourceIPv6Address
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
sourceIPv6Address |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Figure 8
Type:
Length:
sourceIPv6Address:
This TLV (Figure 9) uses format defined in [RFC6929]. Its Type field contains a value that uniquely refers to IPFIX Element sourceTransportPort (7), and its Value field contains IPFIX Element sourceTransportPort, which is the source transport number associated with an internal IPv4 or IPv6 address (refer to [IPFIX]).
IP-Port-Int-Port TLV is included as part of the IP-Port-Forwarding-Map Attribute (refer to Section 3.1.3).
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 | sourceTransportPort
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
sourceTransportPort |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Figure 9
Type:
Length:
sourceTransportPort:
This TLV (Figure 10) uses format defined in [RFC6929]. Its Type field contains a value that uniquely refers to IPFIX Element postNAPTSourceTransportPort (227), and its Value field contains IPFIX Element postNAPTSourceTransportPort, which is the transport number associated with an external IPv4 address(refer to [IPFIX]).
IP-Port-Ext-Port TLV is included as part of the IP-Port-Forwarding-Map Attribute (refer to Section 3.1.3).
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 | postNAPTSourceTransportPort
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
postNAPTSourceTransportPort |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Figure 10
Type:
Length:
postNAPTSourceTransportPort:
This TLV (Figure 11) uses format defined in [RFC6929]. Its Type field contains a value that uniquely refers to IPFIX Element natEvent (230), and its Value field contains IPFIX Element "natEvent", which is a flag to indicate an action of NAT operation (refer to [IPFIX]).
When the value of natEvent is "1" (Create event), it means to allocate a range of transport ports; when the value is "2", it means to de-allocate a range of transports ports. For the purpose of this TLV, no other value is used.
IP-Port-Alloc TLV is included as part of the IP-Port-Range Attribute (refer to Section 3.1.2).
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 | natEvent
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
natEvent |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Figure 11
Type:
Length:
natEvent:
Reserved:
This TLV (Figure 12) uses format defined in [RFC6929]. Its Type field contains a value that uniquely refers to IPFIX Element portRangeStart (361), and its Value field contains IPFIX Element portRangeStart, which is the smallest port number of a range of contiguous transport ports (refer to [IPFIX]).
IP-Port-Range-Start TLV is included as part of the IP-Port-Range Attribute (refer to Section 3.1.2).
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 | portRangeStart
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
portRangeStart |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Figure 12
Type:
TLV8-Length:
portRangeStart:
This TLV (Figure 13) uses format defined in [RFC6929]. Its Type field contains a value that uniquely refers to IPFIX Element portRangeEnd (362), and its Value field contains IPFIX Element portRangeEnd, which is the largest port number of a range of contiguous transport ports (refer to [IPFIX]).
IP-Port-Range-End TLV is included as part of the IP-Port-Range Attribute (refer to Section 3.1.2).
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 | portRangeEnd
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
portRangeEnd |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Figure 13
Type:
Length:
portRangeEnd:
This TLV (Figure 14) uses format defined in [RFC6929]. Its Type field contains a value that uniquely refers to IPFIX Element localID (TBAx3), and its Value field contains IPFIX Element localID, which is a local significant identifier as explained below.
In some CGN deployment scenarios such as DS-Extra-Lite [RFC6619] and Lightweight 4over6 [I-D.ietf-softwire-lw4over6], parameters at a customer premise such as MAC address, interface ID, VLAN ID, PPP session ID, IPv6 prefix, VRF ID, etc., may also be required to pass to the RADIUS server as part of the accounting record.
IP-Port-Local-Id TLV can be included as part of the IP-Port-Range Attribute (refer to Section 3.1.2) and IP-Port-Forwarding-Map Attribute (refer to Section 3.1.3).
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 | localID ....
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Figure 14
Type:
Length:
localID:
This section describes some applications and use cases to illustrate the use of the attributes proposed in this document.
In a broadband network, customer information is usually stored on a RADIUS server, and the BNG hosts the NAS. The communication between the NAS and the RADIUS server is triggered by a subscriber when the user signs in to the Internet service, where either PPP or DHCP/DHCPv6 is used. When a user signs in, the NAS sends a RADIUS Access-Request message to the RADIUS server. The RADIUS server validates the request, and if the validation succeeds, it in turn sends back a RADIUS Access-Accept message. The Access-Accept message carries configuration information specific to that user, back to the NAS, where some of the information would pass on to the requesting user via PPP or DHCP/DHCPv6.
A CGN function in a broadband network would most likely reside on a BNG. In that case, parameters for CGN port/identifier mapping behavior for users can be configured on the RADIUS server. When a user signs in to the Internet service, the associated parameters can be conveyed to the NAS, and proper configuration is accomplished on the CGN device for that user.
Also, CGN operation status such as CGN port/identifier allocation and de-allocation for a specific user on the BNG can also be transmitted back to the RADIUS server for accounting purpose using the RADIUS protocol.
RADIUS protocol has already been widely deployed in broadband networks to manage BNG, thus the functionality described in this specification introduces little overhead to the existing network operation.
In the following sub-sections, we describe how to manage CGN behavior using RADIUS protocol, with required RADIUS extensions proposed in Section 3.
In the face of IPv4 address shortage, there are currently proposals to multiplex multiple subscribers' connections over a smaller number of shared IPv4 addresses, such as Carrier Grade NAT [RFC6888], Dual-Stack Lite [RFC6333], NAT64 [RFC6146], etc. As a result, a single IPv4 public address may be shared by hundreds or even thousands of subscribers. As indicated in [RFC6269], it is therefore necessary to impose limits on the total number of ports available to an individual subscriber to ensure that the shared resource, i.e., the IPv4 address remains available in some capacity to all the subscribers using it, and port limiting is also documented in [RFC6888] as a requirement.
The IP port limit imposed to a specific subscriber may be on the total number of TCP and UDP ports plus the number of ICMP identifiers, or with other granularities as defined in Section 3.1.1.
The per-subscriber based IP port limit is configured on a RADIUS server, along with other user information such as credentials. The value of these IP port limit is based on service agreement and its specification is out of the scope of this document.
When a subscriber signs in to the Internet service successfully, the IP port limit for the subscriber is passed to the BNG based NAS, where CGN also locates, using a new RADIUS attribute called IP-Port-Limit (defined in Section 3.1.1), along with other configuration parameters. While some parameters are passed to the subscriber, the IP port limit is recorded on the CGN device for imposing the usage of TCP/UDP ports and ICMP identifiers for that subscriber.
Figure 15 illustrates how RADIUS protocol is used to configure the maximum number of TCP/UDP ports for a given subscriber on a NAT44 device.
User NAT44/NAS AAA | BNG Server | | | | | | |----Service Request------>| | | | | | |-----Access-Request -------->| | | | | |<----Access-Accept-----------| | | (IP-Port-Limit) | | | (for TCP/UDP ports) | |<---Service Granted ------| | | (other parameters) | | | | | | (NAT44 external port | | allocation and | | IPv4 address assignment) | | | |
Figure 15: RADIUS Message Flow for Configuring NAT44 Port Limit
The IP port limit created on a CGN device for a specific user using RADIUS extension may be changed using RADIUS CoA message [RFC5176] that carries the same RADIUS attribute. The CoA message may be sent from the RADIUS server directly to the NAS, which once accepts and sends back a RADIUS CoA ACK message, the new IP port limit replaces the previous one.
Figure 16 illustrates how RADIUS protocol is used to increase the TCP/UDP port limit from 1024 to 2048 on a NAT44 device for a specific user.
User NAT/NAS AAA | BNG Server | | | | TCP/UDP Port Limit (1024) | | | | | |<---------CoA Request----------| | | (IP-Port-Limit) | | | (for TCP/UDP ports) | | | | | TCP/UDP Port Limit (2048) | | | | | |---------CoA Response--------->| | | |
Figure 16: RADIUS Message Flow for changing a user's NAT44 port limit
Upon obtaining the IP port limit for a subscriber, the CGN device needs to allocate a TCP/UDP port or an ICMP identifiers for the subscriber when receiving a new IP flow sent from that subscriber.
As one practice, a CGN may allocate a bulk of TCP/UDP ports or ICMP identifiers once at a time for a specific user, instead of one port/identifier at a time, and within each port bulk, the ports/identifiers may be randomly distributed or in consecutive fashion. When a CGN device allocates bulk of TCP/UDP ports and ICMP identifiers, the information can be easily conveyed to the RADIUS server by a new RADIUS attribute called the IP-Port-Range (defined in Section 3.1.2). The CGN device may allocate one or more TCP/UDP port ranges or ICMP identifier ranges, or generally called IP port ranges, where each range contains a set of numbers representing TCP/UDP ports or ICMP identifiers, and the total number of ports/identifiers must be less or equal to the associated IP port limit imposed for that subscriber. A CGN device may choose to allocate a small port range, and allocate more at a later time as needed; such practice is good because its randomization in nature.
At the same time, the CGN device also needs to decide the shared IPv4 address for that subscriber. The shared IPv4 address and the pre-allocated IP port range are both passed to the RADIUS server.
When a subscriber initiates an IP flow, the CGN device randomly selects a TCP/UDP port or ICMP identifier from the associated and pre-allocated IP port range for that subscriber to replace the original source TCP/UDP port or ICMP identifier, along with the replacement of the source IP address by the shared IPv4 address.
A CGN device may decide to "free" a previously assigned set of TCP/UDP ports or ICMP identifiers that have been allocated for a specific subscriber but not currently in use, and with that, the CGN device must send the information of the de-allocated IP port range along with the shared IPv4 address to the RADIUS server.
Figure 17 illustrates how RADIUS protocol is used to report a set of ports allocated and de-allocated, respectively, by a NAT44 device for a specific user to the RADIUS server.
Host NAT44/NAS AAA | BNG Server | | | | | | |----Service Request------>| | | | | | |-----Access-Request -------->| | | | | |<----Access-Accept-----------| |<---Service Granted ------| | | (other parameters) | | ... ... ... | | | | | | | (NAT44 decides to allocate | | a TCP/UDP port range for the user) | | | | | |-----Accounting-Request----->| | | (IP-Port-Range | | | for allocation) | ... ... ... | | | | (NAT44 decides to de-allocate | | a TCP/UDP port range for the user) | | | | | |-----Accounting-Request----->| | | (IP-Port-Range | | | for de-allocation) | | | |
Figure 17: RADIUS Message Flow for reporting NAT44 allocation/de-allocation of a port set
In most scenarios, the port mapping on a NAT device is dynamically created when the IP packets of an IP connection initiated by a user arrives. For some applications, the port mapping needs to be pre-defined allowing IP packets of applications from outside a CGN device to pass through and "port forwarded" to the correct user located behind the CGN device.
Port Control Protocol [RFC6887], provides a mechanism to create a mapping from an external IP address and port to an internal IP address and port on a CGN device just to achieve the "port forwarding" purpose. PCP is a server-client protocol capable of creating or deleting a mapping along with a rich set of features on a CGN device in dynamic fashion. In some deployment, all users need is a few, typically just one pre-configured port mapping for applications such as web cam at home, and the lifetime of such a port mapping remains valid throughout the duration of the customer's Internet service connection time. In such an environment, it is possible to statically configure a port mapping on the RADIUS server for a user and let the RADIUS protocol to propagate the information to the associated CGN device.
Figure 18 illustrates how RADIUS protocol is used to configure a forwarding port mapping on a NAT44 device by using RADIUS protocol.
Host NAT/NAS AAA | BNG Server | | | |----Service Request------>| | | | | | |---------Access-Request------->| | | | | |<--------Access-Accept---------| | | (IP-Port-Forwarding-Map) | |<---Service Granted ------| | | (other parameters) | | | | | | (Create a port mapping | | for the user, and | | associate it with the | | internal IP address | | and external IP address) | | | | | | | | |------Accounting-Request------>| | | (IP-Port-Forwarding-Map) |
Figure 18: RADIUS Message Flow for configuring a forwarding port mapping
A port forwarding mapping that is created on a CGN device using RADIUS extension as described above may also be changed using RADIUS CoA message [RFC5176] that carries the same RADIUS associate. The CoA message may be sent from the RADIUS server directly to the NAS, which once accepts and sends back a RADIUS CoA ACK message, the new port forwarding mapping then replaces the previous one.
Figure 19 illustrates how RADIUS protocol is used to change an existing port mapping from (a:X) to (a:Y), where "a" is an internal port, and "X" and "Y" are external ports, respectively, for a specific user with a specific IP address
Host NAT/NAS AAA | BNG Server | | | | Internal IP Address | | Port Map (a:X) | | | | | |<---------CoA Request----------| | | (IP-Port-Forwarding-Map) | | | | | Internal IP Address | | Port Map (a:Y) | | | | | |---------CoA Response--------->| | | (IP-Port-Forwarding-Map) |
Figure 19: RADIUS Message Flow for changing a user's forwarding port mapping
An Internet Service Provider (ISP) assigns TCP/UDP 500 ports for the subscriber Joe. This number is the limit that can be used for TCP/UDP ports on a NAT44 device for Joe, and is configured on a RADIUS server. Also, Joe asks for a pre-defined port forwarding mapping on the NAT44 device for his web cam applications (external port 5000 maps to internal port 80).
When Joe successfully connects to the Internet service, the RADIUS server conveys the TCP/UDP port limit (1000) and the forwarding port mapping (external port 5000 to internal port 80) to the NAT44 device, using IP-Port-Limit attribute and IP-Port-Forwarding-Map attribute, respectively, carried by an Access-Accept message to the BNG where NAS and CGN co-located.
Upon receiving the first outbound IP packet sent from Joe's laptop, the NAT44 device decides to allocate a small port pool that contains 40 consecutive ports, from 3500 to 3540, inclusively, and also assign a shared IPv4 address 192.0.2.15, for Joe. The NAT44 device also randomly selects one port from the allocated range (say 3519) and use that port to replace the original source port in outbound IP packets.
For accounting purpose, the NAT44 device passes this port range (3500-3540) and the shared IPv4 address 192.0.2.15 together to the RADIUS server using IP-Port-Range attribute carried by an Accounting-Request message.
When Joe works on more applications with more outbound IP sessions and the port pool (3500-3540) is close to exhaust, the NAT44 device allocates a second port pool (8500-8800) in a similar fashion, and also passes the new port range (8500-8800) and IPv4 address 192.0.2.15 together to the RADIUS server using IP-Port-Range attribute carried by an Accounting-Request message. Note when the CGN allocates more ports, it needs to assure that the total number of ports allocated for Joe is within the limit.
Joe decides to upgrade his service agreement with more TCP/UDP ports allowed (up to 1000 ports). The ISP updates the information in Joe's profile on the RADIUS server, which then sends a CoA-Request message that carries the IP-Port-Limit attribute with 1000 ports to the NAT44 device; the NAT44 device in turn sends back a CoA-ACK message. With that, Joe enjoys more available TCP/UDP ports for his applications.
When Joe travels, most of the IP sessions are closed with their associated TCP/UDP ports released on the NAT44 device, which then sends the relevant information back to the RADIUS server using IP-Port-Range attribute carried by Accounting-Request message.
Throughout Joe's connection with his ISP Internet service, applications can communicate with his web cam at home from external realm directly traversing the pre-configured mapping on the CGN device.
When Joe disconnects from his Internet service, the CGN device will de-allocate all TCP/UDP ports as well as the port-forwarding mapping, and send the relevant information to the RADIUS server.
Figure 20 illustrates an example of the flow exchange which occurs when a visiting UE connects to a CPE offering WLAN service.
For identification purposes (see [RFC6967]), once the CPE assigns a port set, it issues a RADIUS message to report the assigned port set.
UE CPE NAS AAA | BNG Server | | | | | | |----Service Request------>| | | | | | |-----Access-Request -------->| | | | | |<----Access-Accept-----------| |<---Service Granted ------| | | (other parameters) | | ... | ... ... |<---IP@----| | | | | | | | (CPE assigns a TCP/UDP port | | range for this visiting UE) | | | | | |--Accounting-Request-...------------------->| | | (IP-Port-Range | | | for allocation) | ... | ... ... | | | | | | | | | (CPE withdraws a TCP/UDP port | | range for a visiting UE) | | | | | |--Accounting-Request-...------------------->| | | (IP-Port-Range | | | for de-allocation) | | | |
Figure 20: RADIUS Message Flow for reporting CPE allocation/de-allocation of a port set to a visiting UE
This document proposes three new RADIUS attributes and their formats are as follows:
The following table provides a guide as what type of RADIUS packets that may contain these attributes, and in what quantity.
| Request | Accept | Reject | Challenge | Acct. Request | # | Attribute |
|---|---|---|---|---|---|---|
| 0+ | 0+ | 0 | 0 | 0+ | TBA | IP-Port-Limit |
| 0 | 0 | 0 | 0 | 0+ | TBA | IP-Port-Range |
| 0+ | 0+ | 0 | 0 | 0+ | TBA | IP-Port-Forwarding-Map |
The following table defines the meaning of the above table entries.
| 0 | This attribute MUST NOT be present in packet. |
| 0+ | Zero or more instances of this attribute MAY be present in packet. |
This document does not introduce any security issue than what has been identified in [RFC2865].
This document requires new code point assignments for both IPFIX Elements and RADIUS attributes as explained in the following sections.
The following are code point assignments for new IPFIX Elements as requested by this document:
The following are new code point assignment for RADIUS extensions as requested by this document:
Many thanks to Dan Wing, Roberta Maglione, Daniel Derksen, David Thaler, Alan Dekok, Lionel Morand, and Peter Deacon for their useful comments and suggestions.