draft-ietf-radext-ip-port-radius-ext-07.txt   draft-ietf-radext-ip-port-radius-ext-08.txt 
Network Working Group D. Cheng Network Working Group D. Cheng
Internet-Draft Huawei Internet-Draft Huawei
Intended status: Standards Track J. Korhonen Intended status: Standards Track J. Korhonen
Expires: September 10, 2016 Broadcom Corporation Expires: September 15, 2016 Broadcom Corporation
M. Boucadair M. Boucadair
Orange Orange
S. Sivakumar S. Sivakumar
Cisco Systems Cisco Systems
March 9, 2016 March 14, 2016
RADIUS Extensions for IP Port Configuration and Reporting RADIUS Extensions for IP Port Configuration and Reporting
draft-ietf-radext-ip-port-radius-ext-07 draft-ietf-radext-ip-port-radius-ext-08
Abstract Abstract
This document defines three new RADIUS attributes. For devices that This document defines three new RADIUS attributes. For devices that
implementing IP port ranges, these attributes are used to communicate implementing IP port ranges, these attributes are used to communicate
with a RADIUS server in order to configure and report TCP/UDP ports with a RADIUS server in order to configure and report TCP/UDP ports
and ICMP identifiers, as well as mapping behavior for specific hosts. and ICMP identifiers, as well as mapping behavior for specific hosts.
This mechanism can be used in various deployment scenarios such as This mechanism can be used in various deployment scenarios such as
Carrier Grade NAT, IPv4/IPv6 translators, Provider WLAN Gateway, etc. Carrier-Grade NAT, IPv4/IPv6 translators, Provider WLAN Gateway, etc.
Requirements Language Requirements Language
The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
"SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this
document are to be interpreted as described in RFC 2119 [RFC2119]. document are to be interpreted as described in RFC 2119 [RFC2119].
Status of This Memo Status of This Memo
This Internet-Draft is submitted in full conformance with the This Internet-Draft is submitted in full conformance with the
skipping to change at page 1, line 46 skipping to change at page 1, line 46
Internet-Drafts are working documents of the Internet Engineering Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF). Note that other groups may also distribute Task Force (IETF). Note that other groups may also distribute
working documents as Internet-Drafts. The list of current Internet- working documents as Internet-Drafts. The list of current Internet-
Drafts is at http://datatracker.ietf.org/drafts/current/. Drafts is at http://datatracker.ietf.org/drafts/current/.
Internet-Drafts are draft documents valid for a maximum of six months Internet-Drafts are draft documents valid for a maximum of six months
and may be updated, replaced, or obsoleted by other documents at any and may be updated, replaced, or obsoleted by other documents at any
time. It is inappropriate to use Internet-Drafts as reference time. It is inappropriate to use Internet-Drafts as reference
material or to cite them other than as "work in progress." material or to cite them other than as "work in progress."
This Internet-Draft will expire on September 10, 2016. This Internet-Draft will expire on September 15, 2016.
Copyright Notice Copyright Notice
Copyright (c) 2016 IETF Trust and the persons identified as the Copyright (c) 2016 IETF Trust and the persons identified as the
document authors. All rights reserved. document authors. All rights reserved.
This document is subject to BCP 78 and the IETF Trust's Legal This document is subject to BCP 78 and the IETF Trust's Legal
Provisions Relating to IETF Documents Provisions Relating to IETF Documents
(http://trustee.ietf.org/license-info) in effect on the date of (http://trustee.ietf.org/license-info) in effect on the date of
publication of this document. Please review these documents publication of this document. Please review these documents
skipping to change at page 2, line 26 skipping to change at page 2, line 26
include Simplified BSD License text as described in Section 4.e of include Simplified BSD License text as described in Section 4.e of
the Trust Legal Provisions and are provided without warranty as the Trust Legal Provisions and are provided without warranty as
described in the Simplified BSD License. described in the Simplified BSD License.
Table of Contents Table of Contents
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 3 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 3
2. Terminology . . . . . . . . . . . . . . . . . . . . . . . . . 4 2. Terminology . . . . . . . . . . . . . . . . . . . . . . . . . 4
3. Extensions of RADIUS Attributes and TLVs . . . . . . . . . . 5 3. Extensions of RADIUS Attributes and TLVs . . . . . . . . . . 5
3.1. Extended Attributes for IP Ports . . . . . . . . . . . . 6 3.1. Extended Attributes for IP Ports . . . . . . . . . . . . 6
3.1.1. IP-Port-Limit Attribute . . . . . . . . . . . . . . . 6 3.1.1. IP-Port-Limit-Info Attribute . . . . . . . . . . . . 6
3.1.2. IP-Port-Range Attribute . . . . . . . . . . . . . . . 8 3.1.2. IP-Port-Range Attribute . . . . . . . . . . . . . . . 8
3.1.3. IP-Port-Forwarding-Map Attribute . . . . . . . . . . 10 3.1.3. IP-Port-Forwarding-Map Attribute . . . . . . . . . . 10
3.2. RADIUS TLVs for IP Ports . . . . . . . . . . . . . . . . 13 3.2. RADIUS TLVs for IP Ports . . . . . . . . . . . . . . . . 13
3.2.1. IP-Port-Type TLV . . . . . . . . . . . . . . . . . . 13 3.2.1. IP-Port-Type TLV . . . . . . . . . . . . . . . . . . 13
3.2.2. IP-Port-Limit TLV . . . . . . . . . . . . . . . . . . 14 3.2.2. IP-Port-Limit TLV . . . . . . . . . . . . . . . . . . 14
3.2.3. IP-Port-Ext-IPv4-Addr TLV . . . . . . . . . . . . . . 15 3.2.3. IP-Port-Ext-IPv4-Addr TLV . . . . . . . . . . . . . . 15
3.2.4. IP-Port-Int-IPv4-Addr TLV . . . . . . . . . . . . . . 15 3.2.4. IP-Port-Int-IPv4-Addr TLV . . . . . . . . . . . . . . 16
3.2.5. IP-Port-Int-IPv6-Addr TLV . . . . . . . . . . . . . . 16 3.2.5. IP-Port-Int-IPv6-Addr TLV . . . . . . . . . . . . . . 17
3.2.6. IP-Port-Int-Port TLV . . . . . . . . . . . . . . . . 17 3.2.6. IP-Port-Int-Port TLV . . . . . . . . . . . . . . . . 17
3.2.7. IP-Port-Ext-Port TLV . . . . . . . . . . . . . . . . 18 3.2.7. IP-Port-Ext-Port TLV . . . . . . . . . . . . . . . . 18
3.2.8. IP-Port-Alloc TLV . . . . . . . . . . . . . . . . . . 19 3.2.8. IP-Port-Alloc TLV . . . . . . . . . . . . . . . . . . 19
3.2.9. IP-Port-Range-Start TLV . . . . . . . . . . . . . . . 20 3.2.9. IP-Port-Range-Start TLV . . . . . . . . . . . . . . . 20
3.2.10. IP-Port-Range-End TLV . . . . . . . . . . . . . . . . 21 3.2.10. IP-Port-Range-End TLV . . . . . . . . . . . . . . . . 21
3.2.11. IP-Port-Local-Id TLV . . . . . . . . . . . . . . . . 22 3.2.11. IP-Port-Local-Id TLV . . . . . . . . . . . . . . . . 22
4. Applications, Use Cases and Examples . . . . . . . . . . . . 23 4. Applications, Use Cases and Examples . . . . . . . . . . . . 23
4.1. Managing CGN Port Behavior using RADIUS . . . . . . . . . 23 4.1. Managing CGN Port Behavior using RADIUS . . . . . . . . . 23
4.1.1. Configure IP Port Limit for a User . . . . . . . . . 23 4.1.1. Configure IP Port Limit for a User . . . . . . . . . 24
4.1.2. Report IP Port Allocation/De-allocation . . . . . . . 25 4.1.2. Report IP Port Allocation/Deallocation . . . . . . . 26
4.1.3. Configure Forwarding Port Mapping . . . . . . . . . . 27 4.1.3. Configure Forwarding Port Mapping . . . . . . . . . . 27
4.1.4. An Example . . . . . . . . . . . . . . . . . . . . . 29 4.1.4. An Example . . . . . . . . . . . . . . . . . . . . . 29
4.2. Report Assigned Port Set for a Visiting UE . . . . . . . 30 4.2. Report Assigned Port Set for a Visiting UE . . . . . . . 30
5. Table of Attributes . . . . . . . . . . . . . . . . . . . . . 31 5. Table of Attributes . . . . . . . . . . . . . . . . . . . . . 31
6. Security Considerations . . . . . . . . . . . . . . . . . . . 32 6. Security Considerations . . . . . . . . . . . . . . . . . . . 32
7. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 32 7. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 32
7.1. IANA Considerations on New IPFIX Information Elements . . 32 7.1. IANA Considerations on New IPFIX Information Elements . . 32
7.2. IANA Considerations on New RADIUS Attributes . . . . . . 33 7.2. IANA Considerations on New RADIUS Attributes . . . . . . 33
7.3. IANA Considerations on New RADIUS Nested Attributes . . . 33 7.3. IANA Considerations on New RADIUS TLVs . . . . . . . . . 33
8. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 34 8. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 33
9. References . . . . . . . . . . . . . . . . . . . . . . . . . 34 9. References . . . . . . . . . . . . . . . . . . . . . . . . . 34
9.1. Normative References . . . . . . . . . . . . . . . . . . 34 9.1. Normative References . . . . . . . . . . . . . . . . . . 34
9.2. Informative References . . . . . . . . . . . . . . . . . 35 9.2. Informative References . . . . . . . . . . . . . . . . . 34
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 36 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 36
1. Introduction 1. Introduction
In a broadband network, customer information is usually stored on a In a broadband network, customer information is usually stored on a
RADIUS server [RFC2865]. At the time when a user initiates an IP RADIUS server [RFC2865]. At the time when a user initiates an IP
connection request, if this request is authorized, the RADIUS server connection request, if this request is authorized, the RADIUS server
will populate the user's configuration information to the Network will populate the user's configuration information to the Network
Access Server (NAS), which is often referred to as a Broadband Access Server (NAS), which is often referred to as a Broadband
Network Gateway (BNG) in broadband access networks. The Carrier- Network Gateway (BNG) in broadband access networks. The Carrier-
skipping to change at page 3, line 50 skipping to change at page 3, line 50
the assigned port range in some deployments such as Provider WLAN the assigned port range in some deployments such as Provider WLAN
[I-D.gundavelli-v6ops-community-wifi-svcs]. For example, a visiting [I-D.gundavelli-v6ops-community-wifi-svcs]. For example, a visiting
host can be managed by a CPE (Customer Premises Equipment ) which host can be managed by a CPE (Customer Premises Equipment ) which
will need to report the assigned port range to the service platform. will need to report the assigned port range to the service platform.
This is required for identification purposes (see TR-146 [TR-146] for This is required for identification purposes (see TR-146 [TR-146] for
more details). more details).
This document proposes three new attributes as RADIUS protocol's This document proposes three new attributes as RADIUS protocol's
extensions, and they are used for separate purposes as follows: extensions, and they are used for separate purposes as follows:
1. IP-Port-Limit: This attribute may be carried in RADIUS Access- 1. IP-Port-Limit-Info: This attribute may be carried in RADIUS
Accept, Access-Request, Accounting-Request or CoA-Request packet. Access-Accept, Access-Request, Accounting-Request or CoA-Request
packet. The purpose of this attribute is to limit the total
The purpose of this attribute is to limit the total number of number of TCP/UDP ports and/or ICMP identifiers allocated to a
TCP/UDP ports and/or ICMP identifiers allocated to a user, user, associated with one or more IPv4 addresses.
associated with one or more IPv4 addresses.
2. IP-Port-Range: This attribute may be carried in RADIUS 2. IP-Port-Range: This attribute may be carried in RADIUS
Accounting-Request packet. The purpose of this attribute is to Accounting-Request packet. The purpose of this attribute is to
report by an address sharing device (e.g., a CGN) to the RADIUS report by an address sharing device (e.g., a CGN) to the RADIUS
server the range of TCP/UDP ports and/or ICMP identifiers that server the range of TCP/UDP ports and/or ICMP identifiers that
have been allocated or deallocated associated with a given IPv4 have been allocated or deallocated associated with a given IPv4
address for a user. address for a user.
3. IP-Port-Forwarding-Map: This attribute may be carried in RADIUS 3. IP-Port-Forwarding-Map: This attribute may be carried in RADIUS
Access-Accept, Access-Request, Accounting-Request or CoA-Request Access-Accept, Access-Request, Accounting-Request or CoA-Request
skipping to change at page 5, line 47 skipping to change at page 5, line 47
Note that the definitions of "internal IP address", "internal port", Note that the definitions of "internal IP address", "internal port",
"internal realm", "external IP address", "external port", "external "internal realm", "external IP address", "external port", "external
realm", and "mapping" are the same as defined in Port Control realm", and "mapping" are the same as defined in Port Control
Protocol (PCP) [RFC6887], and the Common Requirements for Carrier- Protocol (PCP) [RFC6887], and the Common Requirements for Carrier-
Grade NATs (CGNs) [RFC6888]. Grade NATs (CGNs) [RFC6888].
3. Extensions of RADIUS Attributes and TLVs 3. Extensions of RADIUS Attributes and TLVs
These three new attributes are defined in the following sub-sections: These three new attributes are defined in the following sub-sections:
1. IP-Port-Limit Attribute 1. IP-Port-Limit-Info Attribute
2. IP-Port-Range Attribute 2. IP-Port-Range Attribute
3. IP-Port-Forwarding-Map Attribute 3. IP-Port-Forwarding-Map Attribute
All these attributes are allocated from the RADIUS "Extended Type" All these attributes are allocated from the RADIUS "Extended Type"
code space per [RFC6929]. code space per [RFC6929].
These attributes and their embedded TLVs (refer to Section 3.2) are
defined with globally unique names and follow the guideline in
Section 2.7.1 of [RFC6929].
In all the figures describing the RADIUS attributes and TLV formats In all the figures describing the RADIUS attributes and TLV formats
in the following sub-sections, the fields are transmitted from left in the following sub-sections, the fields are transmitted from left
to right. to right.
3.1. Extended Attributes for IP Ports 3.1. Extended Attributes for IP Ports
3.1.1. IP-Port-Limit Attribute 3.1.1. IP-Port-Limit-Info Attribute
This attribute is of type "TLV" as defined in the RADIUS Protocol This attribute is of type "TLV" as defined in the RADIUS Protocol
Extensions [RFC6929]. It contains the following sub-attributes: Extensions [RFC6929]. It contains the following sub-attributes:
o an IP-Port-Type TLV (see Section 3.2.1), o an IP-Port-Type TLV (see Section 3.2.1),
o an IP-Port-Limit TLV (see Section 3.2.2), o an IP-Port-Limit TLV (see Section 3.2.2),
o an optional IP-Port-Ext-IPv4-Addr TLV (see Section 3.2.3). o an optional IP-Port-Ext-IPv4-Addr TLV (see Section 3.2.3).
It specifies the maximum number of IP ports as indicated in IP-Port- 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, 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- and associated with a given IPv4 address as indicated in IP-Port-Ext-
IPv4-Addr TLV for an end user. IPv4-Addr TLV for an end user.
Note that when IP-Port-Ext-IPv4-Addr TLV is not included as part of Note that when IP-Port-Ext-IPv4-Addr TLV is not included as part of
the IP-Port-Limit Attribute, the port limit applies to all the IPv4 the IP-Port-Limit-Info Attribute, the port limit applies to all the
addresses managed by the port device, e.g., a CGN or NAT64 device. 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. The IP-Port-Limit-Info Attribute MAY appear in an Access-Accept
It MAY also appear in an Access-Request packet as a preferred maximum packet. It MAY also appear in an Access-Request packet as a
number of IP ports indicated by the device supporting port ranges co- preferred maximum number of IP ports indicated by the device
located with the NAS e.g. a CGN or NAT64. However, the RADIUS server supporting port ranges co-located with the NAS, e.g., a CGN or NAT64.
is not required to honor such a preference. However, the RADIUS server is not required to honor such a
preference.
The IP-Port-Limit Attribute MAY appear in a CoA-Request packet. The IP-Port-Limit-Info Attribute MAY appear in a CoA-Request packet.
The IP-Port-Limit Attribute MAY appear in an Accounting-Request The IP-Port-Limit-Info Attribute MAY appear in an Accounting-Request
packet. packet.
The IP-Port-Limit Attribute MUST NOT appear in any other RADIUS The IP-Port-Limit-Info Attribute MUST NOT appear in any other RADIUS
packet. packet.
The format of the IP-Port-Limit Attribute is shown in Figure 1. The format of the IP-Port-Limit-Info Attribute is shown in Figure 1.
0 1 2 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 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 ... | Type | Length | Extended-Type | Value ...
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Figure 1 Figure 1
Type: Type
241 (To be confirmed by IANA). 241 (To be confirmed by IANA).
Length: Length
This field indicates the total length in bytes of all fields of This field indicates the total length in bytes of all fields of
this attribute, including the Type, Length, Extended-Type, and the this attribute, including the Type, Length, Extended-Type, and the
entire length of the embedded TLVs. entire length of the embedded TLVs.
Extended-Type: Extended-Type
TBA2. TBD1.
Value: Value
This field contains a set of TLVs as follows: This field contains a set of TLVs as follows:
IP-Port-Type TLV: IP-Port-Type TLV
This TLV contains a value that indicates the IP port type. This TLV contains a value that indicates the IP port type.
Refer to Section 3.2.1. Refer to Section 3.2.1.
IP-Port-Limit TLV: IP-Port-Limit TLV
This TLV contains the maximum number of IP ports of a specific This TLV contains the maximum number of IP ports of a specific
IP port type and associated with a given IPv4 address for an IP port type and associated with a given IPv4 address for an
end user. This TLV must be included in the IP-Port-Limit end user. This TLV must be included in the IP-Port-Limit-Info
Attribute. Refer to Section 3.2.2. Attribute. Refer to Section 3.2.2.
IP-Port-Ext-IPv4-Addr TLV: IP-Port-Ext-IPv4-Addr TLV
This TLV contains the IPv4 address that is associated with the This TLV contains the IPv4 address that is associated with the
IP port limit contained in the IP-Port-Limit TLV. This TLV is IP port limit contained in the IP-Port-Limit TLV. This TLV is
optionally included as part of the IP-Port-Limit Attribute. optionally included as part of the IP-Port-Limit-Info
Refer to Section 3.2.3. Attribute. Refer to Section 3.2.3.
IP-Port-Limit attribute is associated with the following identifier: IP-Port-Limit-Info Attribute is associated with the following
241.Extended-Type(TBA2). identifier: 241.Extended-Type(TBD1).
3.1.2. IP-Port-Range Attribute 3.1.2. IP-Port-Range Attribute
This attribute is of type "TLV" as defined in the RADIUS Protocol This attribute is of type "TLV" as defined in the RADIUS Protocol
Extensions [RFC6929]. It contains the following sub-attributes: Extensions [RFC6929]. It contains the following sub-attributes:
o an IP-Port-Type TLV (see Section 3.2.1), o an IP-Port-Type TLV (see Section 3.2.1),
o an IP-Port-Range-Start TLV (see Section 3.2.9), o an IP-Port-Range-Start TLV (see Section 3.2.9),
skipping to change at page 8, line 46 skipping to change at page 8, line 49
deallocated. Both IP-Port-Ext-IPv4-Addr TLV and IP-Port-Local-Id TLV 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 are optional and if included, they are used by a port device (e.g., a
CGN device) to identify the end user. CGN device) to identify the end user.
The IP-Port-Range Attribute MAY appear in an Accounting-Request The IP-Port-Range Attribute MAY appear in an Accounting-Request
packet. packet.
The IP-Port-Range Attribute MUST NOT appear in any other RADIUS The IP-Port-Range Attribute MUST NOT appear in any other RADIUS
packet. packet.
The format of the IP-Port-Range Attribute format is shown in The format of the IP-Port-Range Attribute is shown in Figure 2.
Figure 2. The fields are transmitted from left to right.
0 1 2 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 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 ... | Type | Length | Extended-Type | Value ...
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Figure 2 Figure 2
Type: Type
241 (To be confirmed by IANA). 241 (To be confirmed by IANA).
Length: Length
This field indicates the total length in bytes of all fields of This field indicates the total length in bytes of all fields of
this attribute, including the Type, Length, Extended-Type, and the this attribute, including the Type, Length, Extended-Type, and the
entire length of the embedded TLVs. entire length of the embedded TLVs.
Extended-Type: Extended-Type
TBA3. TBD2.
Value: Value
This field contains a set of TLVs as follows: This field contains a set of TLVs as follows:
IP-Port-Type TLV: IP-Port-Type TLV
This TLV contains a value that indicates the IP port type. This TLV contains a value that indicates the IP port type.
Refer to Section 3.2.1. Refer to Section 3.2.1.
IP-Port-Alloc TLV: IP-Port-Alloc TLV
This TLV contains a flag to indicate that the range of the This TLV contains a flag to indicate that the range of the
specified IP ports for either allocation or deallocation. This specified IP ports for either allocation or deallocation. This
TLV must be included as part of the IP-Port-Range Attribute. TLV must be included as part of the IP-Port-Range Attribute.
Refer to Section 3.2.8. Refer to Section 3.2.8.
IP-Port-Range-Start TLV: IP-Port-Range-Start TLV
This TLV contains the smallest port number of a range of This TLV contains the smallest port number of a range of
contiguous IP ports. To report the port allocation, this TLV contiguous IP ports. To report the port allocation, this TLV
must be included together with IP-Port-Range-End TLV as part of must be included together with IP-Port-Range-End TLV as part of
the IP-Port-Range Attribute. Refer to Section 3.2.9. the IP-Port-Range Attribute. Refer to Section 3.2.9.
IP-Port-Range-End TLV: IP-Port-Range-End TLV
This TLV contains the largest port number of a range of This TLV contains the largest port number of a range of
contiguous IP ports. To report the port allocation, this TLV contiguous IP ports. To report the port allocation, this TLV
must be included together with IP-Port-Range-Start TLV as part must be included together with IP-Port-Range-Start TLV as part
of the IP-Port-Range Attribute. Refer to Section 3.2.10. of the IP-Port-Range Attribute. Refer to Section 3.2.10.
IP-Port-Ext-IPv4-Addr TLV: IP-Port-Ext-IPv4-Addr TLV
This TLV contains the IPv4 address that is associated with the This TLV contains the IPv4 address that is associated with the
IP port range, as collectively indicated in the IP-Port-Range- IP port range, as collectively indicated in the IP-Port-Range-
Start TLV and the IP-Port-Range-End TLV. This TLV is Start TLV and the IP-Port-Range-End TLV. This TLV is
optionally included as part of the IP-Port-Range Attribute. optionally included as part of the IP-Port-Range Attribute.
Refer to Section 3.2.3. Refer to Section 3.2.3.
IP-Port-Local-Id TLV: IP-Port-Local-Id TLV
This TLV contains a local session identifier at the customer This TLV contains a local session identifier at the customer
premise, such as MAC address, interface ID, VLAN ID, PPP premise, such as MAC address, interface ID, VLAN ID, PPP
sessions ID, VRF ID, IPv6 address/prefix, etc. This TLV is sessions ID, VRF ID, IPv6 address/prefix, etc. This TLV is
optionally included as part of the IP-Port-Range Attribute. optionally included as part of the IP-Port-Range Attribute.
Refer to Section 3.2.11. Refer to Section 3.2.11.
The IP-Port-Range attribute is associated with the following The IP-Port-Range attribute is associated with the following
identifier: 241.Extended-Type(TBA3). identifier: 241.Extended-Type(TBD2).
3.1.3. IP-Port-Forwarding-Map Attribute 3.1.3. IP-Port-Forwarding-Map Attribute
This attribute is of type "TLV" as defined in the RADIUS Protocol This attribute is of type "TLV" as defined in the RADIUS Protocol
Extensions [RFC6929]. It contains the following sub-attributes: Extensions [RFC6929]. It contains the following sub-attributes:
o an IP-Port-Type TLV (see Section 3.2.1), o an IP-Port-Type TLV (see Section 3.2.1),
o an IP-Port-Int-Port TLV (see Section 3.2.6), o an IP-Port-Int-Port TLV (see Section 3.2.6),
skipping to change at page 11, line 32 skipping to change at page 11, line 32
Figure 3. Figure 3.
0 1 2 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 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 .... | Type | Length | Extended-Type | Value ....
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Figure 3 Figure 3
Type: Type
241 (To be confirmed by IANA). 241 (To be confirmed by IANA).
Length: Length
This field indicates the total length in bytes of all fields of This field indicates the total length in bytes of all fields of
this attribute, including the Type, Length, Extended-Type, and the this attribute, including the Type, Length, Extended-Type, and the
entire length of the embedded TLVs. entire length of the embedded TLVs.
Extended-Type: Extended-Type
TBA4. TBD3.
Value: Value
This field contains a set of TLVs as follows: This field contains a set of TLVs as follows:
IP-Port-Type TLV: IP-Port-Type TLV
This TLV contains a value that indicates the IP port type. This TLV contains a value that indicates the IP port type.
Refer to Section 3.2.1. Refer to Section 3.2.1.
IP-Port-Int-Port TLV: IP-Port-Int-Port TLV
This TLV contains an internal IP port number associated with an This TLV contains an internal IP port number associated with an
internal IPv4 or IPv6 address. This TLV must be included internal IPv4 or IPv6 address. This TLV must be included
together with IP-Port-Ext-Port TLV as part of the IP-Port- together with IP-Port-Ext-Port TLV as part of the IP-Port-
Forwarding-Map attribute. Refer to Section 3.2.6. Forwarding-Map attribute. Refer to Section 3.2.6.
IP-Port-Ext-Port TLV: IP-Port-Ext-Port TLV
This TLV contains an external IP port number associated with an This TLV contains an external IP port number associated with an
external IPv4 address. This TLV must be included together with external IPv4 address. This TLV must be included together with
IP-Port-Int-Port TLV as part of the IP-Port-Forwarding-Map IP-Port-Int-Port TLV as part of the IP-Port-Forwarding-Map
attribute. Refer to Section 3.2.7. attribute. Refer to Section 3.2.7.
IP-Port-Int-IPv4-Addr TLV: IP-Port-Int-IPv4-Addr TLV
This TLV contains an IPv4 address that is associated with the This TLV contains an IPv4 address that is associated with the
internal IP port number contained in the IP-Port-Int-Port TLV. internal IP port number contained in the IP-Port-Int-Port TLV.
For IPv4 network, either this TLV or IP-Port-Local-Id TLV must For IPv4 network, either this TLV or IP-Port-Local-Id TLV must
be included as part of the IP-Port-Forwarding-Map Attribute. be included as part of the IP-Port-Forwarding-Map Attribute.
Refer to Section 3.2.4. Refer to Section 3.2.4.
IP-Port-Int-IPv6-Addr TLV: IP-Port-Int-IPv6-Addr TLV
This TLV contains an IPv4 address that is associated with the This TLV contains an IPv4 address that is associated with the
internal IP port number contained in the IP-Port-Int-Port TLV. internal IP port number contained in the IP-Port-Int-Port TLV.
For IPv6 network, either this TLV or IP-Port-Local-Id TLV must For IPv6 network, either this TLV or IP-Port-Local-Id TLV must
be included as part of the IP-Port-Forwarding-Map Attribute. be included as part of the IP-Port-Forwarding-Map Attribute.
Refer to Section 3.2.5. Refer to Section 3.2.5.
IP-Port-Local-Id TLV: IP-Port-Local-Id TLV
This TLV contains a local session identifier at the customer This TLV contains a local session identifier at the customer
premise, such as MAC address, interface ID, VLAN ID, PPP premise, such as MAC address, interface ID, VLAN ID, PPP
sessions ID, VRF ID, IPv6 address/prefix, etc. Either this TLV sessions ID, VRF ID, IPv6 address/prefix, etc. Either this TLV
or IP-Port-Int-IP-Addr TLV must be included as part of the IP- or IP-Port-Int-IP-Addr TLV must be included as part of the IP-
Port-Forwarding-Map Attribute. Refer to Section 3.2.11. Port-Forwarding-Map Attribute. Refer to Section 3.2.11.
IP-Port-Ext-IPv4-Addr TLV: IP-Port-Ext-IPv4-Addr TLV
This TLV contains an IPv4 address that is associated with the This TLV contains an IPv4 address that is associated with the
external IP port number contained in the IP-Port-Ext-Port TLV. external IP port number contained in the IP-Port-Ext-Port TLV.
This TLV may be included as part of the IP-Port-Forwarding-Map This TLV may be included as part of the IP-Port-Forwarding-Map
Attribute. Refer to Section 3.2.3. Attribute. Refer to Section 3.2.3.
The IP-Port-Forwarding-Map attribute is associated with the following The IP-Port-Forwarding-Map Attribute is associated with the following
identifier: 241.Extended-Type(TBA4). identifier: 241.Extended-Type(TBD3).
3.2. RADIUS TLVs for IP Ports 3.2. RADIUS TLVs for IP Ports
The TLVs that are included in the three attributes (see Section 3.1)
are defined in the following sub-sections. These TLVs use the format
defined in [RFC6929].
3.2.1. IP-Port-Type TLV 3.2.1. IP-Port-Type TLV
This TLV (Figure 4) uses the format defined in [RFC6929]. Its "Type" The format of IP-Port-Type TLV is shown in Figure 4. Its "Type"
field contains a value that uniquely refers to IPFIX Information field contains a value that uniquely refers to IPFIX Information
Element "transportType" (TBAx1), and its "Value" field contains the Element "transportType" (TBAx1), and its "Value" field contains the
values defined for the IPFIX Information Element "transportType", values defined for the IPFIX Information Element "transportType",
which indicates the type of IP transport as follows: which indicates the type of IP transport as follows:
1: 1:
Refer to TCP port, UDP port, and ICMP identifier as a whole. Refer to TCP port, UDP port, and ICMP identifier as a whole.
2: 2:
skipping to change at page 13, line 38 skipping to change at page 13, line 42
Refer to TCP port only. Refer to TCP port only.
4: 4:
Refer to UDP port only. Refer to UDP port only.
5: 5:
Refer to ICMP identifier only. Refer to ICMP identifier only.
IP-Port-Type TLV is 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
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 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 | TLV-Type | Length | transportType
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
transportType | transportType |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Figure 4 Figure 4
Type: TLV-Type
1. This MUST uniquely refer to the IPFIX Information Element
The value depends on the encapsulating attribute (see IANA identifier TBAx1.
Section). This MUST uniquely refer to the IPFIX Information
Element identifier TBAx1.
Length: Length
6. 6.
transportType: transportType
Integer. This field contains the data (unsigned8) of Integer. This field contains the data (unsigned8) of
transportType (TBAx1) defined in IPFIX, right justified, and the transportType (TBAx1) defined in IPFIX, right justified, and the
unused bits in this field MUST be set to zero. unused bits in this field MUST be set to zero.
IP-Port-Type TLV is included in the following Attributes:
o IP-Port-Limit-Info Attribute, identified as 241.TBD1.1 (see
Section 3.1.1).
o IP-Port-Range Attribute, identified as 241.TBD2.1 (see
Section 3.1.2).
o IP-Port-Forwarding-Mapping Attribute, identified as 241.TBD3.1
(see Section 3.1.3).
3.2.2. IP-Port-Limit TLV 3.2.2. IP-Port-Limit TLV
This TLV (Figure 5) uses the format defined in [RFC6929]. Its "Type" The format of IP-Port-Limit TLV is shown in Figure 5. Its "Type"
field contains a value that uniquely refers to IPFIX Information field contains a value that uniquely refers to IPFIX Information
Element natTransportLimit (TBAx2), and its "Value" field contains Element natTransportLimit (TBAx2), and its "Value" field contains
IPFIX Information Element natTransportLimit, which indicates the IPFIX Information Element natTransportLimit, which indicates the
maximum number of ports for a given IPv4 address assigned to a user maximum number of ports for a given IPv4 address assigned to a user
for a specified IP-Port-Type. for a specified IP-Port-Type.
IP-Port-Limit TLV is included as part of the IP-Port-Limit Attribute
(refer to Section 3.1.1).
0 1 2 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 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 | TLV-Type | Length | natTransportLimit
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
natTransportLimit | natTransportLimit |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Figure 5 Figure 5
Type: TLV-Type
TBD2.2. It MUST uniquely refer to the IPFIX Information Element 2. It MUST uniquely refer to the IPFIX Information Element
identifier TBAx2. identifier TBAx2.
Length: Length
6. 6.
natTransportLimit: natTransportLimit
Integer. This field contains the data (unsigned16) of Integer. This field contains the data (unsigned16) of
natTransportLimit (TBAx2) defined in IPFIX, right justified, and natTransportLimit (TBAx2) defined in IPFIX, right justified, and
the unused bits in this field MUST be set to zero. the unused bits in this field MUST be set to zero.
3.2.3. IP-Port-Ext-IPv4-Addr TLV IP-Port-Limit TLV is included as part of the IP-Port-Limit-Info
Attribute (refer to Section 3.1.1), identified as 241.TBD1.2.
This TLV (Figure 6) uses the format defined in[RFC6929]. Its "Type" 3.2.3. IP-Port-Ext-IPv4-Addr TLV
field contains a value that uniquely refers to IPFIX Information
Element postNATSourceIPv4Address(225), and its "Value" field contains
IPFIX Information Element postNATSourceIPv4Address, which is the IPv4
source address after NAT operation (refer to [IPFIX]).
IP-Port-Ext-IPv4-Addr TLV MAY be included as part of the IP-Port- The format of IP-Port-Ext-IPv4-Addr TLV is shown in Figure 6. Its
Limit Attribute (refer to Section 3.1.1), IP-Port-Range Attribute "Type" field contains a value that uniquely refers to IPFIX
(refer to Section 3.1.2), and IP-Port-Forwarding-Map Attribute (refer Information Element postNATSourceIPv4Address(225), and its "Value"
to Section 3.1.3). field contains IPFIX Information Element postNATSourceIPv4Address,
which is the IPv4 source address after NAT operation (refer to
[IPFIX]).
0 1 2 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 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 | TLV-Type | Length | postNATSourceIPv4Address
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
postNATSourceIPv4Address | postNATSourceIPv4Address |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Figure 6 Figure 6
Type: TLV-Type
The value depends on the encapsulating attribute (see IANA 3. This MUST uniquely refer to the IPFIX Information Element
section). This MUST uniquely refer to the IPFIX Information identifier 225.
Element identifier 225.
Length: Length
6 6
postNATSourceIPv4Address: postNATSourceIPv4Address
Integer. This field contains the data (ipv4Address) of Integer. This field contains the data (ipv4Address) of
postNATSourceIPv4Address (225) defined in IPFIX. postNATSourceIPv4Address (225) defined in IPFIX.
IP-Port-Ext-IPv4-Addr TLV MAY be included in the following
Attributes:
o IP-Port-Limit-Info Attribute, identified as 241.TBD1.3 (see
Section 3.1.1).
o IP-Port-Range Attribute, identified as 241.TBD2.3 (see
Section 3.1.2).
o IP-Port-Forwarding-Mapping Attribute, identified as 241.TBD3.3
(see Section 3.1.3).
3.2.4. IP-Port-Int-IPv4-Addr TLV 3.2.4. IP-Port-Int-IPv4-Addr TLV
This TLV (Figure 7) uses format defined in [RFC6929]. Its "Type" The format of IP-Port-Int-IPv4 TLV is shown in Figure 7. Its "Type"
field contains a value that uniquely refers to IPFIX Information field contains a value that uniquely refers to IPFIX Information
Element sourceIPv4Address (8), and its "Value" field contains IPFIX Element sourceIPv4Address (8), and its "Value" field contains IPFIX
Information Element sourceIPv4Address, which is the IPv4 source Information Element sourceIPv4Address, which is the IPv4 source
address before NAT operation (refer to [IPFIX]). address before NAT operation (refer to [IPFIX]).
IP-Port-Int-IPv4-Addr TLV MAY 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
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 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 | TLV-Type | Length | sourceIPv4Address
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
sourceIPv4Address | sourceIPv4Address |
+-+--+-+-+-+-+-+-++-+-+-+-+-+-+-+ +-+--+-+-+-+-+-+-++-+-+-+-+-+-+-+
Figure 7 Figure 7
Type: TLV-Type
TBD4.3. It MUST uniquely refer to the IPFIX Information Element 4. It MUST uniquely refer to the IPFIX Information Element
identifier 8. identifier 8.
Length: Length
6. 6.
sourceIPv4Address: sourceIPv4Address
Integer. This field contains the data (ipv4Address) of Integer. This field contains the data (ipv4Address) of
sourceIPv4Address (8) defined in IPFIX. sourceIPv4Address (8) defined in IPFIX.
3.2.5. IP-Port-Int-IPv6-Addr TLV IP-Port-Int-IPv4-Addr TLV MAY be included as part of the IP-Port-
Forwarding-Map Attribute (refer to Section 3.1.3), identified as
241.TBD3.4.
This TLV (Figure 8) uses format defined in [RFC6929]. Its "Type" 3.2.5. IP-Port-Int-IPv6-Addr TLV
field contains a value that uniquely refers to IPFIX Information
Element sourceIPv6Address(27), and its "Value" field contains IPFIX
Information Element sourceIPv6Address, which is the IPv6 source
address before NAT operation (refer to [IPFIX]).
IP-Port-Int-IPv6-Addr TLV MAY be included as part of the IP-Port- The format of IP-Port-Int-IPv6-Addr TLV is shown in Figure 8. Its
Forwarding-Map Attribute (refer to Section 3.1.3). "Type" field contains a value that uniquely refers to IPFIX
Information Element sourceIPv6Address(27), and its "Value" field
contains IPFIX Information Element sourceIPv6Address, which is the
IPv6 source address before NAT operation (refer to [IPFIX]).
0 1 2 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 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 | TLV-Type | Length | sourceIPv6Address
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
sourceIPv6Address sourceIPv6Address
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
sourceIPv6Address sourceIPv6Address
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
sourceIPv6Address sourceIPv6Address
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
sourceIPv6Address | sourceIPv6Address |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Figure 8 Figure 8
Type: TLV-Type
TBD4.4. It MUST uniquely refer to the IPFIX Information Element 5. It MUST uniquely refer to the IPFIX Information Element
identifier 27. identifier 27.
Length: Length
18. 18.
sourceIPv6Address: sourceIPv6Address
IPv6 address (128 bits). This field contains the data IPv6 address (128 bits). This field contains the data
(ipv6Address) of sourceIPv6Address (27) defined in IPFIX. (ipv6Address) of sourceIPv6Address (27) defined in IPFIX.
IP-Port-Int-IPv6-Addr TLV MAY be included as part of the IP-Port-
Forwarding-Map Attribute (refer to Section 3.1.3), identified as
241.TBD3.5.
3.2.6. IP-Port-Int-Port TLV 3.2.6. IP-Port-Int-Port TLV
This TLV (Figure 9) uses format defined in [RFC6929]. Its "Type" The format of IP-Port-Int-Port TLV is shown in Figure 9. Its "Type"
field contains a value that uniquely refers to IPFIX Information field contains a value that uniquely refers to IPFIX Information
Element sourceTransportPort (7), and its "Value" field contains IPFIX Element sourceTransportPort (7), and its "Value" field contains IPFIX
Information Element sourceTransportPort, which is the source Information Element sourceTransportPort, which is the source
transport number associated with an internal IPv4 or IPv6 address transport number associated with an internal IPv4 or IPv6 address
(refer to [IPFIX]). (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
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 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 | TLV-Type | Length | sourceTransportPort
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
sourceTransportPort | sourceTransportPort |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Figure 9 Figure 9
Type: TLV-Type
TBD4.5. It MUST uniquely refer to the IPFIX Information Element 6. It MUST uniquely refer to the IPFIX Information Element
identifier 7. identifier 7.
Length: Length
4. 4.
sourceTransportPort: sourceTransportPort
Integer. This field contains the data (unsigned16) of Integer. This field contains the data (unsigned16) of
sourceTrasnportPort (7) defined in IPFIX, right justified, and sourceTrasnportPort (7) defined in IPFIX, right justified, and
unused bits MUST be set to zero. unused bits MUST be set to zero.
IP-Port-Int-Port TLV is included as part of the IP-Port-Forwarding-
Map Attribute (refer to Section 3.1.3), identified as 241.TBD3.6.
3.2.7. IP-Port-Ext-Port TLV 3.2.7. IP-Port-Ext-Port TLV
This TLV (Figure 10) uses format defined in [RFC6929]. Its "Type" The format of IP-Port-Ext-Port TLV is shown in Figure 10. Its "Type"
field contains a value that uniquely refers to IPFIX Information field contains a value that uniquely refers to IPFIX Information
Element postNAPTSourceTransportPort (227), and its "Value" field Element postNAPTSourceTransportPort (227), and its "Value" field
contains IPFIX Information Element postNAPTSourceTransportPort, which contains IPFIX Information Element postNAPTSourceTransportPort, which
is the transport number associated with an external IPv4 is the transport number associated with an external IPv4
address(refer to [IPFIX]). 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
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 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 | TLV-Type | Length | postNAPTSourceTransportPort
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
postNAPTSourceTransportPort | postNAPTSourceTransportPort |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Figure 10 Figure 10
Type: TLV-Type
TBD4.6. It MUST uniquely refer to the IPFIX Information Element 7. It MUST uniquely refer to the IPFIX Information Element
identifier 227 . identifier 227 .
Length: Length
6. 6.
postNAPTSourceTransportPort: postNAPTSourceTransportPort
Integer. This field contains the data (unsigned16) of Integer. This field contains the data (unsigned16) of
postNAPTSourceTrasnportPort (227) defined in IPFIX, right postNAPTSourceTrasnportPort (227) defined in IPFIX, right
justified, and unused bits must be set to zero. justified, and unused bits must be set to zero.
IP-Port-Ext-Port TLV is included as part of the IP-Port-Forwarding-
Map Attribute (refer to Section 3.1.3), identified as 241.TBD3.7.
3.2.8. IP-Port-Alloc TLV 3.2.8. IP-Port-Alloc TLV
This TLV (Figure 11) uses format defined in [RFC6929]. Its "Type" The format of IP-Port-Alloc TLV is shown in Figure 11. Its "Type"
field contains a value that uniquely refers to IPFIX Information field contains a value that uniquely refers to IPFIX Information
Element natEvent (230), and its "Value" field contains IPFIX Element natEvent (230), and its "Value" field contains IPFIX
Information Element "natEvent", which is a flag to indicate an action Information Element "natEvent", which is a flag to indicate an action
of NAT operation (refer to [IPFIX]). of NAT operation (refer to [IPFIX]).
When the value of natEvent is "1" (Create event), it means to 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 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 to deallocate a range of transports ports. For the purpose of this
TLV, no other value is used. 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
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 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 | TLV-Type | Length | natEvent
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
natEvent | natEvent |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Figure 11 Figure 11
Type: TLV-Type
TBD3.3. It MUST uniquely refer to the IPFIX Information Element 8. It MUST uniquely refer to the IPFIX Information Element
identifier 230 . identifier 230 .
Length: Length
3. 3.
natEvent: natEvent
Integer. This field contains the data (unsigned8) of natEvent Integer. This field contains the data (unsigned8) of natEvent
(230) defined in IPFIX, right justified, and unused bits must be (230) defined in IPFIX, right justified, and unused bits must be
set to zero. It indicates the allocation or deallocation of a set to zero. It indicates the allocation or deallocation of a
range of IP ports as follows: range of IP ports as follows:
1: 1:
Allocation Allocation
2: 2:
Deallocation Deallocation
Reserved: Reserved:
0. 0.
3.2.9. IP-Port-Range-Start TLV IP-Port-Alloc TLV is included as part of the IP-Port-Range Attribute
(refer to Section 3.1.2), identified as 241.TBD2.8.
This TLV (Figure 12) uses format defined in [RFC6929]. Its "Type" 3.2.9. IP-Port-Range-Start TLV
field contains a value that uniquely refers to IPFIX Information
Element portRangeStart (361), and its "Value" field contains IPFIX
Information 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 The format of IP-Port-Range-Start TLV is shown in Figure 12. Its
Attribute (refer to Section 3.1.2). "Type" field contains a value that uniquely refers to IPFIX
Information Element portRangeStart (361), and its "Value" field
contains IPFIX Information Element portRangeStart, which is the
smallest port number of a range of contiguous transport ports (refer
to [IPFIX]).
0 1 2 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 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 | TLV-Type | Length | portRangeStart
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
portRangeStart | portRangeStart |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Figure 12 Figure 12
Type: TLV-Type
TBD3.4. It MUST uniquely refer to the IPFIX Information Element 9. It MUST uniquely refer to the IPFIX Information Element
identifier 361. identifier 361.
TLV8-Length: Length
4. 4.
portRangeStart: portRangeStart
Integer. This field contains the data (unsigned16) of (361) Integer. This field contains the data (unsigned16) of (361)
defined in IPFIX, right justified, and unused bits must be set to defined in IPFIX, right justified, and unused bits must be set to
zero. zero.
3.2.10. IP-Port-Range-End TLV IP-Port-Range-Start TLV is included as part of the IP-Port-Range
Attribute (refer to Section 3.1.2), identified as 241.TBD2.9.
This TLV (Figure 13) uses format defined in [RFC6929]. Its "Type" 3.2.10. IP-Port-Range-End TLV
field contains a value that uniquely refers to IPFIX Information
Element portRangeEnd (362), and its "Value" field contains IPFIX
Information 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 The format of IP-Port-Range-End TLV is shown in Figure 13. Its
Attribute (refer to Section 3.1.2). "Type" field contains a value that uniquely refers to IPFIX
Information Element portRangeEnd (362), and its "Value" field
contains IPFIX Information Element portRangeEnd, which is the largest
port number of a range of contiguous transport ports (refer to
[IPFIX]).
0 1 2 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 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 | TLV-Type | Length | portRangeEnd
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
portRangeEnd | portRangeEnd |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Figure 13 Figure 13
Type: TLV-Type
TBD3.5. It MUST uniquely refer to the IPFIX Information Element 10. It MUST uniquely refer to the IPFIX Information Element
identifier 362. identifier 362.
Length: Length
4. The Length field for IP-Port-Range-End TLV. 4. The Length field for IP-Port-Range-End TLV.
portRangeEnd: portRangeEnd
Integer. This field contains the data (unsigned16) of (362) Integer. This field contains the data (unsigned16) of (362)
defined in IPFIX, right justified, and unused bits must be set to defined in IPFIX, right justified, and unused bits must be set to
zero. zero.
IP-Port-Range-End TLV is included as part of the IP-Port-Range
Attribute (refer to Section 3.1.2), identified as 241.TBD2.10.
3.2.11. IP-Port-Local-Id TLV 3.2.11. IP-Port-Local-Id TLV
This TLV (Figure 14) uses format defined in [RFC6929]. Its "Type" The format of IP-Port-Local-Id TLV is shown in Figure 14. Its "Type"
field contains a value that uniquely refers to the IPFIX Information field contains a value that uniquely refers to the IPFIX Information
Element localID (TBAx3), and its "Value" field contains IPFIX Element localID (TBAx3), and its "Value" field contains IPFIX
Information Element localID, which is a local significant identifier Information Element localID, which is a local significant identifier
as explained below. as explained below.
In some CGN deployment scenarios such as DS-Extra-Lite [RFC6619] and In some CGN deployment scenarios such as DS-Extra-Lite [RFC6619] and
Lightweight 4over6 [RFC7596], parameters at a customer premise such Lightweight 4over6 [RFC7596], parameters at a customer premise such
as MAC address, interface ID, VLAN ID, PPP session ID, IPv6 prefix, 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 VRF ID, etc., may also be required to pass to the RADIUS server as
part of the accounting record. part of the accounting record.
IP-Port-Local-Id TLV MAY 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
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 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 .... | TLV-Type | Length | localID ....
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Figure 14 Figure 14
Type: TLV-Type
The value depends on the encapsulating attribute (see IANA 11. This MUST uniquely refer to the IPFIX Information Element
section). This MUST uniquely refer to the IPFIX Information identifier TBAx3.
Element identifier TBAx3.
Length: Length
Variable number of bytes. Variable number of bytes.
localID: localID
string. This field contains the data (string) of (TBAx3) defined string. This field contains the data (string) of (TBAx3) defined
in IPFIX. This is a local session identifier at the customer in IPFIX. This is a local session identifier at the customer
premise, such as MAC address, interface ID, VLAN ID, PPP sessions premise, such as MAC address, interface ID, VLAN ID, PPP sessions
ID, VRF ID, IPv6 address/prefix, etc. ID, VRF ID, IPv6 address/prefix, etc.
IP-Port-Local-Id TLV MAY be included in the following Attributes:
o IP-Port-Range Attribute, identified as 241.TBD2.11 (see
Section 3.1.2).
o IP-Port-Forwarding-Mapping Attribute, identified as 241.TBD3.11
(see Section 3.1.3).
4. Applications, Use Cases and Examples 4. Applications, Use Cases and Examples
This section describes some applications and use cases to illustrate This section describes some applications and use cases to illustrate
the use of the attributes proposed in this document. the use of the attributes proposed in this document.
4.1. Managing CGN Port Behavior using RADIUS 4.1. Managing CGN Port Behavior using RADIUS
In a broadband network, customer information is usually stored on a In a broadband network, customer information is usually stored on a
RADIUS server, and the BNG acts as a NAS. The communication between RADIUS server, and the BNG acts as a NAS. The communication between
the NAS and the RADIUS server is triggered by a user when it signs in the NAS and the RADIUS server is triggered by a user when it signs in
skipping to change at page 23, line 32 skipping to change at page 24, line 16
DHCPv6. DHCPv6.
A CGN function in a broadband network would most likely co-located on A CGN function in a broadband network would most likely co-located on
a BNG. In that case, parameters for CGN port/identifier mapping a BNG. In that case, parameters for CGN port/identifier mapping
behavior for users can be configured on the RADIUS server. When a behavior for users can be configured on the RADIUS server. When a
user signs in to the Internet service, the associated parameters can user signs in to the Internet service, the associated parameters can
be conveyed to the NAS, and proper configuration is accomplished on be conveyed to the NAS, and proper configuration is accomplished on
the CGN device for that user. the CGN device for that user.
Also, CGN operation status such as CGN port/identifier allocation and Also, CGN operation status such as CGN port/identifier allocation and
de-allocation for a specific user on the BNG can also be transmitted deallocation for a specific user on the BNG can also be transmitted
back to the RADIUS server for accounting purpose using the RADIUS back to the RADIUS server for accounting purpose using the RADIUS
protocol. protocol.
RADIUS protocol has already been widely deployed in broadband RADIUS protocol has already been widely deployed in broadband
networks to manage BNG, thus the functionality described in this networks to manage BNG, thus the functionality described in this
specification introduces little overhead to the existing network specification introduces little overhead to the existing network
operation. operation.
In the following sub-sections, we describe how to manage CGN behavior In the following sub-sections, we describe how to manage CGN behavior
using RADIUS protocol, with required RADIUS extensions proposed in using RADIUS protocol, with required RADIUS extensions proposed in
skipping to change at page 24, line 22 skipping to change at page 25, line 8
with other granularities as defined in Section 3.1.1. with other granularities as defined in Section 3.1.1.
The per-user based IP port limit is configured on a RADIUS server, The per-user based IP port limit is configured on a RADIUS server,
along with other user information such as credentials. The value of along with other user information such as credentials. The value of
this IP port limit is based on service agreement and its this IP port limit is based on service agreement and its
specification is out of the scope of this document. specification is out of the scope of this document.
When a user signs in to the Internet service successfully, the IP When a user signs in to the Internet service successfully, the IP
port limit for the subscriber is passed by the RADIUS server to the port limit for the subscriber is passed by the RADIUS server to the
BNG, acting as a NAS and co-located with the CGN, using a new RADIUS BNG, acting as a NAS and co-located with the CGN, using a new RADIUS
attribute called IP-Port-Limit (defined in Section 3.1.1), along with attribute called IP-Port-Limit-Info (defined in Section 3.1.1), along
other configuration parameters. While some parameters are passed to with other configuration parameters. While some parameters are
the user, the IP port limit is recorded on the CGN device for passed to the user, the IP port limit is recorded on the CGN device
imposing the usage of TCP/UDP ports and ICMP identifiers for that for imposing the usage of TCP/UDP ports and ICMP identifiers for that
user. user.
Figure 15 illustrates how RADIUS protocol is used to configure the Figure 15 illustrates how RADIUS protocol is used to configure the
maximum number of TCP/UDP ports for a given user on a NAT44 device. maximum number of TCP/UDP ports for a given user on a NAT44 device.
User NAT44/NAS AAA User NAT44/NAS AAA
| BNG Server | BNG Server
| | | | | |
| | | | | |
|----Service Request------>| | |----Service Request------>| |
| | | | | |
| |-----Access-Request -------->| | |-----Access-Request -------->|
| | | | | |
| |<----Access-Accept-----------| | |<----Access-Accept-----------|
| | (IP-Port-Limit) | | | (IP-Port-Limit-Info) |
| | (for TCP/UDP ports) | | | (for TCP/UDP ports) |
|<---Service Granted ------| | |<---Service Granted ------| |
| (other parameters) | | | (other parameters) | |
| | | | | |
| (NAT44 external port | | (NAT44 external port |
| allocation and | | allocation and |
| IPv4 address assignment) | | IPv4 address assignment) |
| | | | | |
Figure 15: RADIUS Message Flow for Configuring NAT44 Port Limit Figure 15: RADIUS Message Flow for Configuring NAT44 Port Limit
skipping to change at page 25, line 22 skipping to change at page 26, line 11
Figure 16 illustrates how RADIUS protocol is used to increase the 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 TCP/UDP port limit from 1024 to 2048 on a NAT44 device for a specific
user. user.
User NAT44/NAS AAA User NAT44/NAS AAA
| BNG Server | BNG Server
| | | | | |
| TCP/UDP Port Limit (1024) | | TCP/UDP Port Limit (1024) |
| | | | | |
| |<---------CoA Request----------| | |<---------CoA Request----------|
| | (IP-Port-Limit) | | | (IP-Port-Limit-Info) |
| | (for TCP/UDP ports) | | | (for TCP/UDP ports) |
| | | | | |
| TCP/UDP Port Limit (2048) | | TCP/UDP Port Limit (2048) |
| | | | | |
| |---------CoA Response--------->| | |---------CoA Response--------->|
| | | | | |
Figure 16: RADIUS Message Flow for changing a user's NAT44 port limit Figure 16: RADIUS Message Flow for changing a user's NAT44 port limit
4.1.2. Report IP Port Allocation/De-allocation 4.1.2. Report IP Port Allocation/Deallocation
Upon obtaining the IP port limit for a user, the CGN device needs to Upon obtaining the IP port limit for a user, the CGN device needs to
allocate a TCP/UDP port or an ICMP identifiers for the user when allocate a TCP/UDP port or an ICMP identifiers for the user when
receiving a new IP flow sent from that user. receiving a new IP flow sent from that user.
As one practice, a CGN may allocate a bulk of TCP/UDP ports or ICMP 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/ identifiers once at a time for a specific user, instead of one port/
identifier at a time, and within each port bulk, the ports/ identifier at a time, and within each port bulk, the ports/
identifiers may be randomly distributed or in consecutive fashion. identifiers may be randomly distributed or in consecutive fashion.
When a CGN device allocates bulk of TCP/UDP ports and ICMP When a CGN device allocates bulk of TCP/UDP ports and ICMP
skipping to change at page 26, line 20 skipping to change at page 27, line 8
When a user initiates an IP flow, the CGN device randomly selects a When a user initiates an IP flow, the CGN device randomly selects a
TCP/UDP port or ICMP identifier from the associated and pre-allocated TCP/UDP port or ICMP identifier from the associated and pre-allocated
IP port range for that user to replace the original source TCP/UDP IP port range for that user to replace the original source TCP/UDP
port or ICMP identifier, along with the replacement of the source IP port or ICMP identifier, along with the replacement of the source IP
address by the shared IPv4 address. address by the shared IPv4 address.
A CGN device may decide to "free" a previously assigned set of TCP/ 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 UDP ports or ICMP identifiers that have been allocated for a specific
user but not currently in use, and with that, the CGN device must user 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 send the information of the deallocated IP port range along with the
shared IPv4 address to the RADIUS server. shared IPv4 address to the RADIUS server.
Figure 17 illustrates how RADIUS protocol is used to report a set of Figure 17 illustrates how RADIUS protocol is used to report a set of
ports allocated and de-allocated, respectively, by a NAT44 device for ports allocated and deallocated, respectively, by a NAT44 device for
a specific user to the RADIUS server. a specific user to the RADIUS server.
Host NAT44/NAS AAA Host NAT44/NAS AAA
| BNG Server | BNG Server
| | | | | |
| | | | | |
|----Service Request------>| | |----Service Request------>| |
| | | | | |
| |-----Access-Request -------->| | |-----Access-Request -------->|
| | | | | |
skipping to change at page 27, line 27 skipping to change at page 27, line 37
| | | | | |
| | | | | |
| (NAT44 decides to allocate | | (NAT44 decides to allocate |
| a TCP/UDP port range for the user) | | a TCP/UDP port range for the user) |
| | | | | |
| |-----Accounting-Request----->| | |-----Accounting-Request----->|
| | (IP-Port-Range | | | (IP-Port-Range |
| | for allocation) | | | for allocation) |
... ... ... ... ... ...
| | | | | |
| (NAT44 decides to de-allocate | | (NAT44 decides to deallocate |
| a TCP/UDP port range for the user) | | a TCP/UDP port range for the user) |
| | | | | |
| |-----Accounting-Request----->| | |-----Accounting-Request----->|
| | (IP-Port-Range | | | (IP-Port-Range |
| | for de-allocation) | | | for deallocation) |
| | | | | |
Figure 17: RADIUS Message Flow for reporting NAT44 allocation/de- Figure 17: RADIUS Message Flow for reporting NAT44 allocation/
allocation of a port set deallocation of a port set
4.1.3. Configure Forwarding Port Mapping 4.1.3. Configure Forwarding Port Mapping
In most scenarios, the port mapping on a NAT device is dynamically 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 created when the IP packets of an IP connection initiated by a user
arrives. For some applications, the port mapping needs to be pre- arrives. For some applications, the port mapping needs to be pre-
defined allowing IP packets of applications from outside a CGN device defined allowing IP packets of applications from outside a CGN device
to pass through and "port forwarded" to the correct user located to pass through and "port forwarded" to the correct user located
behind the CGN device. behind the CGN device.
skipping to change at page 29, line 34 skipping to change at page 29, line 44
An Internet Service Provider (ISP) assigns TCP/UDP 500 ports for the An Internet Service Provider (ISP) assigns TCP/UDP 500 ports for the
user Joe. This number is the limit that can be used for TCP/UDP ports user 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. 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 Also, Joe asks for a pre-defined port forwarding mapping on the NAT44
device for his web cam applications (external port 5000 maps to device for his web cam applications (external port 5000 maps to
internal port 80). internal port 80).
When Joe successfully connects to the Internet service, the RADIUS When Joe successfully connects to the Internet service, the RADIUS
server conveys the TCP/UDP port limit (1000) and the forwarding port server conveys the TCP/UDP port limit (1000) and the forwarding port
mapping (external port 5000 to internal port 80) to the NAT44 device, mapping (external port 5000 to internal port 80) to the NAT44 device,
using IP-Port-Limit attribute and IP-Port-Forwarding-Map attribute, using IP-Port-Limit-Info Attribute and IP-Port-Forwarding-Map
respectively, carried by an Access-Accept message to the BNG where attribute, respectively, carried by an Access-Accept message to the
NAS and CGN co-located. BNG where NAS and CGN co-located.
Upon receiving the first outbound IP packet sent from Joe's laptop, Upon receiving the first outbound IP packet sent from Joe's laptop,
the NAT44 device decides to allocate a small port pool that contains the NAT44 device decides to allocate a small port pool that contains
40 consecutive ports, from 3500 to 3540, inclusively, and also assign 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 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 randomly selects one port from the allocated range (say 3519) and use
that port to replace the original source port in outbound IP packets. that port to replace the original source port in outbound IP packets.
For accounting purpose, the NAT44 device passes this port range For accounting purpose, the NAT44 device passes this port range
(3500-3540) and the shared IPv4 address 192.0.2.15 together to the (3500-3540) and the shared IPv4 address 192.0.2.15 together to the
skipping to change at page 30, line 14 skipping to change at page 30, line 24
allocates a second port pool (8500-8800) in a similar fashion, and allocates a second port pool (8500-8800) in a similar fashion, and
also passes the new port range (8500-8800) and IPv4 address also passes the new port range (8500-8800) and IPv4 address
192.0.2.15 together to the RADIUS server using IP-Port-Range 192.0.2.15 together to the RADIUS server using IP-Port-Range
attribute carried by an Accounting-Request message. Note when the attribute carried by an Accounting-Request message. Note when the
CGN allocates more ports, it needs to assure that the total number of CGN allocates more ports, it needs to assure that the total number of
ports allocated for Joe is within the limit. ports allocated for Joe is within the limit.
Joe decides to upgrade his service agreement with more TCP/UDP ports 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 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 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 that carries the IP-Port-Limit-Info Attribute with 1000 ports to the
device; the NAT44 device in turn sends back a CoA-ACK message. With NAT44 device; the NAT44 device in turn sends back a CoA-ACK message.
that, Joe enjoys more available TCP/UDP ports for his applications. With that, Joe enjoys more available TCP/UDP ports for his
applications.
When Joe travels, most of the IP sessions are closed with their When Joe travels, most of the IP sessions are closed with their
associated TCP/UDP ports released on the NAT44 device, which then associated TCP/UDP ports released on the NAT44 device, which then
sends the relevant information back to the RADIUS server using IP- sends the relevant information back to the RADIUS server using IP-
Port-Range attribute carried by Accounting-Request message. Port-Range attribute carried by Accounting-Request message.
Throughout Joe's connection with his ISP Internet service, Throughout Joe's connection with his ISP Internet service,
applications can communicate with his web cam at home from external applications can communicate with his web cam at home from external
realm directly traversing the pre-configured mapping on the CGN realm directly traversing the pre-configured mapping on the CGN
device. device.
When Joe disconnects from his Internet service, the CGN device will When Joe disconnects from his Internet service, the CGN device will
de-allocate all TCP/UDP ports as well as the port-forwarding mapping, deallocate all TCP/UDP ports as well as the port-forwarding mapping,
and send the relevant information to the RADIUS server. and send the relevant information to the RADIUS server.
4.2. Report Assigned Port Set for a Visiting UE 4.2. Report Assigned Port Set for a Visiting UE
Figure 20 illustrates an example of the flow exchange which occurs Figure 20 illustrates an example of the flow exchange which occurs
when a visiting UE connects to a CPE offering WLAN service. when a visiting UE connects to a CPE offering WLAN service.
For identification purposes (see [RFC6967]), once the CPE assigns a For identification purposes (see [RFC6967]), once the CPE assigns a
port set, it issues a RADIUS message to report the assigned port set. port set, it issues a RADIUS message to report the assigned port set.
skipping to change at page 31, line 33 skipping to change at page 31, line 33
| | (IP-Port-Range | | | (IP-Port-Range |
| | for allocation) | | | for allocation) |
... | ... ... ... | ... ...
| | | | | | | |
| | | | | | | |
| (CPE withdraws a TCP/UDP port | | (CPE withdraws a TCP/UDP port |
| range for a visiting UE) | | range for a visiting UE) |
| | | | | |
| |--Accounting-Request-...------------------->| | |--Accounting-Request-...------------------->|
| | (IP-Port-Range | | | (IP-Port-Range |
| | for de-allocation) | | | for deallocation) |
| | | | | |
Figure 20: RADIUS Message Flow for reporting CPE allocation/de- Figure 20: RADIUS Message Flow for reporting CPE allocation/
allocation of a port set to a visiting UE deallocation of a port set to a visiting UE
5. Table of Attributes 5. Table of Attributes
This document proposes three new RADIUS attributes and their formats This document proposes three new RADIUS attributes and their formats
are as follows: are as follows:
o IP-Port-Limit: 241.TBA2. o IP-Port-Limit-Info: 241.TBD1.
o IP-Port-Range: 241.TBA3. o IP-Port-Range: 241.TBD2.
o IP-Port-Forwarding-Map: 241.TBA4. o IP-Port-Forwarding-Map: 241.TBD3.
Note to IANA: it is assumed that Extended-Type-1 "241" will be used Note to IANA: it is assumed that Extended-Type-1 "241" will be used
for theses attributes. for these attributes.
The following table provides a guide as what type of RADIUS packets The following table provides a guide as what type of RADIUS packets
that may contain these attributes, and in what quantity. that may contain these attributes, and in what quantity.
Request Accept Reject Challenge Acct. # Attribute Request Accept Reject Challenge Acct. # Attribute
Request Request
0+ 0+ 0 0 0+ TBA IP-Port-Limit 0+ 0+ 0 0 0+ TBA IP-Port-Limit-Info
0 0 0 0 0+ TBA IP-Port-Range 0 0 0 0 0+ TBA IP-Port-Range
0+ 0+ 0 0 0+ TBA IP-Port-Forwarding-Map 0+ 0+ 0 0 0+ TBA IP-Port-Forwarding-Map
The following table defines the meaning of the above table entries. The following table defines the meaning of the above table entries.
0 This attribute MUST NOT be present in packet. 0 This attribute MUST NOT be present in packet.
0+ Zero or more instances of this attribute MAY be present in packet. 0+ Zero or more instances of this attribute MAY be present in packet.
6. Security Considerations 6. Security Considerations
This document does not introduce any security issue other than the This document does not introduce any security issue other than the
ones already identified in RADIUS [RFC2865]. ones already identified in RADIUS [RFC2865].
7. IANA Considerations 7. IANA Considerations
This document requires new code point assignments for both IPFIX This document requires new code point assignments for both IPFIX
Information Elements and RADIUS attributes as explained in the Information Elements and RADIUS attributes as explained in the
following sub-sections. following sub-sections.
It is assumed that Extended-Type-1 "241" will be used for RADIUS
attributes in Section 7.2.
7.1. IANA Considerations on New IPFIX Information Elements 7.1. IANA Considerations on New IPFIX Information Elements
The following are code point assignments for new IPFIX Information The following are code point assignments for new IPFIX Information
Elements as requested by this document: Elements as requested by this document:
o transportType (refer to Section 3.2.1): The identifier of this o transportType (refer to Section 3.2.1): The identifier of this
IPFIX Information Element is TBAx1. The data type of this IPFIX IPFIX Information Element is TBAx1. The data type of this IPFIX
Information Element is unsigned8, and the Element's value Information Element is unsigned8, and the Element's value
indicates TCP/UDP ports and ICMP Identifiers (1), TCP/UDP ports indicates TCP/UDP ports and ICMP Identifiers (1), TCP/UDP ports
(2), TCP ports (3), UDP ports (4) or ICMP identifiers (5). (2), TCP ports (3), UDP ports (4) or ICMP identifiers (5).
skipping to change at page 33, line 16 skipping to change at page 33, line 18
The authors request that Attribute Types and Attribute Values defined The authors request that Attribute Types and Attribute Values defined
in this document be registered by the Internet Assigned Numbers in this document be registered by the Internet Assigned Numbers
Authority (IANA) from the RADIUS namespaces as described in the "IANA Authority (IANA) from the RADIUS namespaces as described in the "IANA
Considerations" section of [RFC3575], in accordance with BCP 26 Considerations" section of [RFC3575], in accordance with BCP 26
[RFC5226]. For RADIUS packets, attributes and registries created by [RFC5226]. For RADIUS packets, attributes and registries created by
this document IANA is requested to place them at this document IANA is requested to place them at
http://www.iana.org/assignments/radius-types. http://www.iana.org/assignments/radius-types.
In particular, this document defines three new RADIUS attributes, In particular, this document defines three new RADIUS attributes,
entitled "IP-Port-Limit" (see Section 3.1.1), "IP-Port-Range" (see entitled "IP-Port-Limit-Info" (see Section 3.1.1), "IP-Port-Range"
Section 3.1.2) and "IP-Port-Forwarding-Map" (see Section 3.1.3), with (see Section 3.1.2) and "IP-Port-Forwarding-Map" (see Section 3.1.3),
assigned values of 241.TBD2, 241.TBD3 and 241.TBD4 from the Short with assigned values of 241.TBD1, 241.TBD2 and 241.TBD3 from the
Extended Space of [RFC6929]: Short Extended Space of [RFC6929]:
Type Name Meaning
---- ---- -------
241.TBD2 IP-Port-Limit see Section 3.1.1
241.TBD3 IP-Port-Range see Section 3.1.2
241.TBD4 IP-Port-Forwarding-Map see Section 3.1.3
7.3. IANA Considerations on New RADIUS Nested Attributes
This specification requests allocation of the following TLVs within
the attribute IP-Port-Limit 241.TBD2:
Type Name Meaning Type Name Meaning
---- ---- ------- ---- ---- -------
241.TBD2.1 IP-Port-Type see Section 3.2.1 241.TBD1 IP-Port-Limit-Info see Section 3.1.1
241.TBD2.2 IP-Port-Limit see Section 3.2.2 241.TBD2 IP-Port-Range see Section 3.1.2
241.TBD2.3 IP-Port-Ext-IPv4-Addr see Section 3.2.3 241.TBD3 IP-Port-Forwarding-Map see Section 3.1.3
This specification requests allocation of the following TLVs within
the attribute IP-Port-Range 241.TBD3:
Type Name Meaning 7.3. IANA Considerations on New RADIUS TLVs
---- ---- -------
241.TBD3.1 IP-Port-Type see Section 3.2.1
241.TBD3.2 IP-Port-Ext-IPv4-Addr see Section 3.2.3
241.TBD3.3 IP-Port-Alloc see Section 3.2.8
241.TBD3.4 IP-Port-Range-Start see Section 3.2.9
241.TBD3.5 IP-Port-Range-End see Section 3.2.10
This specification requests allocation of the following TLVs within This specification requests allocation of the following TLVs:
the attribute IP-Port-Forwarding-Map 241.TBD4:
Type Name Meaning Name Value Meaning
---- ---- ------- ---- ----- -------
241.TBD4.1 IP-Port-Type see Section 3.2.1 IP-Port-Type 1 see Section 3.2.1
241.TBD4.2 IP-Port-Ext-IPv4-Addr see Section 3.2.3 IP-Port-Limit 2 see Section 3.2.2
241.TBD4.3 IP-Port-Int-IPv4-Addr see Section 3.2.4 IP-Port-Ext-IPv4-Addr 3 see Section 3.2.3
241.TBD4.4 IP-Port-Int-IPv6-Addr see Section 3.2.5 IP-Port-Int-IPv4-Addr 4 see Section 3.2.4
241.TBD4.5 IP-Port-Int-Port see Section 3.2.6 IP-Port-Int-IPv6-Addr 5 see Section 3.2.5
241.TBD4.6 IP-Port-Ext-Port see Section 3.2.7 IP-Port-Int-Port 6 see Section 3.2.6
241.TBD4.7 IP-Port-Local-Id see Section 3.2.11 IP-Port-Ext-Port 7 see Section 3.2.7
IP-Port-Alloc 8 see Section 3.2.8
IP-Port-Range-Start 9 see Section 3.2.9
IP-Port-Range-End 10 see Section 3.2.10
IP-Port-Local-Id 11 see Section 3.2.11
8. Acknowledgements 8. Acknowledgements
Many thanks to Dan Wing, Roberta Maglione, Daniel Derksen, David Many thanks to Dan Wing, Roberta Maglione, Daniel Derksen, David
Thaler, Alan Dekok, Lionel Morand, and Peter Deacon for their useful Thaler, Alan Dekok, Lionel Morand, and Peter Deacon for their useful
comments and suggestions. comments and suggestions.
Special thanks to Lionel Morand for the Shepherd review. Special thanks to Lionel Morand for the Shepherd review.
9. References 9. References
 End of changes. 172 change blocks. 
271 lines changed or deleted 282 lines changed or added

This html diff was produced by rfcdiff 1.44. The latest version is available from http://tools.ietf.org/tools/rfcdiff/