draft-ietf-radext-ip-port-radius-ext-17.txt   rfc8045.txt 
Network Working Group D. Cheng Internet Engineering Task Force (IETF) D. Cheng
Internet-Draft Huawei Request for Comments: 8045 Huawei
Intended status: Standards Track J. Korhonen Category: Standards Track J. Korhonen
Expires: May 18, 2017 Broadcom Corporation ISSN: 2070-1721 Broadcom Corporation
M. Boucadair M. Boucadair
Orange Orange
S. Sivakumar S. Sivakumar
Cisco Systems Cisco Systems
November 14, 2016 January 2017
RADIUS Extensions for IP Port Configuration and Reporting RADIUS Extensions for IP Port Configuration and Reporting
draft-ietf-radext-ip-port-radius-ext-17
Abstract Abstract
This document defines three new RADIUS attributes. For devices that This document defines three new RADIUS attributes. For devices that
implement IP port ranges, these attributes are used to communicate implement IP port ranges, these attributes are used to communicate
with a RADIUS server in order to configure and report IP transport with a RADIUS server in order to configure and report IP transport
ports, as well as mapping behavior for specific hosts. This ports as well as mapping behavior for specific hosts. This mechanism
mechanism can be used in various deployment scenarios such as can be used in various deployment scenarios such as Carrier-Grade
Carrier-Grade NAT, IPv4/IPv6 translators, Provider WLAN Gateway, etc. NAT, IPv4/IPv6 translators, Provider WLAN gateway, etc. This
This document defines a mapping between some RADIUS attributes and document defines a mapping between some RADIUS attributes and IP Flow
IPFIX Information Element Identifiers. Information Export (IPFIX) Information Element identifiers.
Requirements Language
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].
Status of This Memo Status of This Memo
This Internet-Draft is submitted in full conformance with the This is an Internet Standards Track document.
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 This document is a product of the Internet Engineering Task Force
and may be updated, replaced, or obsoleted by other documents at any (IETF). It represents the consensus of the IETF community. It has
time. It is inappropriate to use Internet-Drafts as reference received public review and has been approved for publication by the
material or to cite them other than as "work in progress." Internet Engineering Steering Group (IESG). Further information on
Internet Standards is available in Section 2 of RFC 7841.
This Internet-Draft will expire on May 18, 2017. Information about the current status of this document, any errata,
and how to provide feedback on it may be obtained at
http://www.rfc-editor.org/info/rfc8045.
Copyright Notice Copyright Notice
Copyright (c) 2016 IETF Trust and the persons identified as the Copyright (c) 2017 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
carefully, as they describe your rights and restrictions with respect carefully, as they describe your rights and restrictions with respect
to this document. Code Components extracted from this document must to this document. Code Components extracted from this document must
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 ....................................................4
2. Terminology . . . . . . . . . . . . . . . . . . . . . . . . . 4 2. Terminology .....................................................5
3. Extensions of RADIUS Attributes and TLVs . . . . . . . . . . 5 2.1. Requirements Language ......................................6
3.1. Extended Attributes for IP Ports . . . . . . . . . . . . 6 3. Extensions of RADIUS Attributes and TLVs ........................7
3.1.1. IP-Port-Limit-Info Attribute . . . . . . . . . . . . 6 3.1. Extended Attributes for IP Ports ...........................7
3.1.2. IP-Port-Range Attribute . . . . . . . . . . . . . . . 8 3.1.1. IP-Port-Limit-Info Attribute ........................7
3.1.3. IP-Port-Forwarding-Map Attribute . . . . . . . . . . 11 3.1.2. IP-Port-Range Attribute .............................9
3.2. RADIUS TLVs for IP Ports . . . . . . . . . . . . . . . . 13 3.1.3. IP-Port-Forwarding-Map Attribute ...................12
3.2.1. IP-Port-Type TLV . . . . . . . . . . . . . . . . . . 14 3.2. RADIUS TLVs for IP Ports ..................................15
3.2.2. IP-Port-Limit TLV . . . . . . . . . . . . . . . . . . 15 3.2.1. IP-Port-Type TLV ...................................16
3.2.3. IP-Port-Ext-IPv4-Addr TLV . . . . . . . . . . . . . . 16 3.2.2. IP-Port-Limit TLV ..................................17
3.2.4. IP-Port-Int-IPv4-Addr TLV . . . . . . . . . . . . . . 16 3.2.3. IP-Port-Ext-IPv4-Addr TLV ..........................18
3.2.5. IP-Port-Int-IPv6-Addr TLV . . . . . . . . . . . . . . 17 3.2.4. IP-Port-Int-IPv4-Addr TLV ..........................19
3.2.6. IP-Port-Int-Port TLV . . . . . . . . . . . . . . . . 18 3.2.5. IP-Port-Int-IPv6-Addr TLV ..........................20
3.2.7. IP-Port-Ext-Port TLV . . . . . . . . . . . . . . . . 19 3.2.6. IP-Port-Int-Port TLV ...............................21
3.2.8. IP-Port-Alloc TLV . . . . . . . . . . . . . . . . . . 20 3.2.7. IP-Port-Ext-Port TLV ...............................22
3.2.9. IP-Port-Range-Start TLV . . . . . . . . . . . . . . . 21 3.2.8. IP-Port-Alloc TLV ..................................23
3.2.10. IP-Port-Range-End TLV . . . . . . . . . . . . . . . . 22 3.2.9. IP-Port-Range-Start TLV ............................24
3.2.11. IP-Port-Local-Id TLV . . . . . . . . . . . . . . . . 22 3.2.10. IP-Port-Range-End TLV .............................25
4. Applications, Use Cases and Examples . . . . . . . . . . . . 24 3.2.11. IP-Port-Local-Id TLV ..............................25
4.1. Managing CGN Port Behavior using RADIUS . . . . . . . . . 24 4. Applications, Use Cases, and Examples ..........................27
4.1.1. Configure IP Port Limit for a User . . . . . . . . . 24 4.1. Managing CGN Port Behavior Using RADIUS ...................27
4.1.2. Report IP Port Allocation/Deallocation . . . . . . . 26 4.1.1. Configure IP Port Limit for a User .................27
4.1.3. Configure Forwarding Port Mapping . . . . . . . . . . 28 4.1.2. Report IP Port Allocation/Deallocation .............29
4.1.4. An Example . . . . . . . . . . . . . . . . . . . . . 30 4.1.3. Configure Port Forwarding Mapping ..................31
4.2. Report Assigned Port Set for a Visiting UE . . . . . . . 31 4.1.4. An Example .........................................33
5. Table of Attributes . . . . . . . . . . . . . . . . . . . . . 32 4.2. Report Assigned Port Set for a Visiting UE ................35
6. Security Considerations . . . . . . . . . . . . . . . . . . . 33 5. Table of Attributes ............................................36
7. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 34 6. Security Considerations ........................................36
7.1. IANA Considerations on New IPFIX Information 7. IANA Considerations ............................................37
Elements . . . . . . . . . . . . . . . . . . . . . . . . 34 7.1. New IPFIX Information Elements ............................37
7.2. New RADIUS Attributes .....................................38
7.2. IANA Considerations on New RADIUS Attributes . . . . . . 34 7.3. New RADIUS TLVs ...........................................38
7.3. IANA Considerations on New RADIUS TLVs . . . . . . . . . 35 8. References .....................................................39
8. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 35 8.1. Normative References ......................................39
9. References . . . . . . . . . . . . . . . . . . . . . . . . . 36 8.2. Informative References ....................................40
9.1. Normative References . . . . . . . . . . . . . . . . . . 36 Acknowledgments ...................................................43
9.2. Informative References . . . . . . . . . . . . . . . . . 37 Authors' Addresses ................................................43
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 39
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-
Grade NAT (CGN) function may also be implemented on the BNG. Within Grade NAT (CGN) function may also be implemented on the BNG. Within
this document, the CGN may perform NAT44 [RFC3022], NAT64 [RFC6146], this document, the CGN may perform Network Address Translation from
or Dual-Stack Lite AFTR [RFC6333] function. In such case, the CGN IP IPv4 Clients to IPv4 Servers (NAT44) [RFC3022], NAT from IPv6 Clients
transport port (e.g., TCP/UDP port) mapping(s) behavior(s) can be to IPv4 Servers (NAT64) [RFC6146], or Dual-Stack Lite Address Family
part of the configuration information sent from the RADIUS server to Transition Router (AFTR) [RFC6333] function. In such case, the CGN
the NAS/BNG. The NAS/BNG may also report to the RADIUS Server the IP IP transport port (e.g., TCP/UDP port) mapping behaviors can be part
port mapping behavior applied by the CGN to a user session to the of the configuration information sent from the RADIUS server to the
RADIUS server, as part of the accounting information sent from the NAS/BNG. As part of the accounting information sent from the NAS/BNG
NAS/BNG to a RADIUS server. to a RADIUS server, the NAS/BNG may also report the IP port mapping
behavior applied by the CGN to a user session.
When IP packets traverse the CGN, it performs mapping on the IP When IP packets traverse the CGN, it performs mapping on the IP
transport (e.g., TCP/UDP) source port as required. An IP transport transport (e.g., TCP/UDP) source port as required. An IP transport
source port, along with source IP address, destination IP address, source port, along with a source IP address, destination IP address,
destination port and protocol identifier if applicable, uniquely destination port, and protocol identifier, if applicable, uniquely
identify a mapping. Since the number space of IP transport ports in identify a mapping. Since the number space of IP transport ports in
CGN's external realm is shared among multiple users assigned with the the CGN's external realm is shared among multiple users assigned with
same IPv4 address, the total number of a user's simultaneous IP the same IPv4 address, the total number of a user's simultaneous IP
mappings is likely to be subject to port quota (see Section 5 of mappings is likely to be subject to a port quota (see Section 5 of
[RFC6269]). [RFC6269]).
The attributes defined in this document may also be used to report The attributes defined in this document may also be used to report
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 [WIFI-SERVICES]. For example, a visiting host can be managed by
host can be managed by a CPE (Customer Premises Equipment ) which Customer Premises Equipment (CPE), which will need to report the
will need to report the assigned port range to the service platform. assigned port range to the service platform. This is required for
This is required for identification purposes (see TR-146 [TR-146] 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
extensions, and they are used for separate purposes as follows: extensions; they are used for separate purposes, as follows:
1. IP-Port-Limit-Info: This attribute may be carried in a RADIUS 1. IP-Port-Limit-Info: This attribute may be carried in a RADIUS
Access-Accept, Access-Request, Accounting-Request or CoA-Request Access-Accept, Access-Request, Accounting-Request, or CoA-Request
packet. The purpose of this attribute is to limit the total packet. The purpose of this attribute is to limit the total
number of IP source transport ports allocated to a user, number of IP source transport ports allocated to a user and
associated with one or more IPv4 or IPv6 addresses. associated with one or more IPv4 or IPv6 addresses.
2. IP-Port-Range: This attribute may be carried in a RADIUS 2. IP-Port-Range: This attribute may be carried in a RADIUS
Accounting-Request packet. The purpose of this attribute is for Accounting-Request packet. The purpose of this attribute is for
an address sharing device (e.g., a CGN) to report to the RADIUS an address-sharing device (e.g., a CGN) to report to the RADIUS
server the range of IP source transport ports that have been server the range of IP source transport ports that have been
allocated or deallocated for a user. The port range is bound to allocated or deallocated for a user. The port range is bound to
an external IPv4 address. an external IPv4 address.
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
packet. The purpose of this attribute is to specify how an IP packet. The purpose of this attribute is to specify how an IP
internal source transport port together with its internal IPv4 or internal source transport port, together with its internal IPv4
IPv6 address are mapped to an external source transport port or IPv6 address, are mapped to an external source transport port
along with the external IPv4 address. along with the external IPv4 address.
IPFIX Information Elements [RFC7012] can be used for IP flow IPFIX Information Elements [RFC7012] can be used for IP flow
identification and representation over RADIUS. This document identification and representation over RADIUS. This document
provides a mapping between some RADIUS TLVs and IPFIX Information provides a mapping between some RADIUS TLVs and IPFIX Information
Element Identifiers. A new IPFIX Information Element is defined by Element identifiers. A new IPFIX Information Element is defined by
this document (see Section 3.2.2). this document (see Section 3.2.2).
IP protocol numbers (refer to [ProtocolNumbers]) can be used for IP protocol numbers (refer to [ProtocolNumbers]) can be used for
identification of IP transport protocols (e.g., TCP [RFC0793], UDP identification of IP transport protocols (e.g., TCP [RFC793], UDP
[RFC0768], DCCP [RFC4340], and SCTP [RFC4960]) that are associated [RFC768], Datagram Congestion Control Protocol (DCCP) [RFC4340], and
with some RADIUS attributes. Stream Control Transmission Protocol (SCTP) [RFC4960]) that are
associated with some RADIUS attributes.
This document focuses on IPv4 address sharing. IPv6 prefix sharing This document focuses on IPv4 address sharing. Mechanisms for IPv6
mechanisms (e.g., NPTv6) are out of scope. prefix sharing (e.g., IPv6-to-IPv6 Network Prefix Translation
(NPTv6)) are out of scope.
2. Terminology 2. Terminology
This document makes use of the following terms: This document makes use of the following terms:
o IP Port: refers to IP transport port (e.g., TCP port number, UDP o IP Port: This refers to an IP transport port (e.g., a TCP port
port number). number or UDP port number).
o IP Port Type: refers to the IP transport protocol as indicated by o IP Port Type: This refers to the IP transport protocol as
the IP transport protocol number, refer to (refer to indicated by the IP transport protocol number. Refer to
[ProtocolNumbers]) [ProtocolNumbers].
o IP Port Limit: denotes the maximum number of IP ports for a o IP Port Limit: This denotes the maximum number of IP ports for a
specific (or all) IP transport protocol(s), that a device specific (or all) IP transport protocol(s) that a device
supporting port ranges can use when performing port number supporting port ranges can use when performing port number
mappings for a specific user/host. Note, this limit is usually mappings for a specific user/host. Note that this limit is
associated with one or more IPv4/IPv6 addresses. usually associated with one or more IPv4/IPv6 addresses.
o IP Port Range: specifies a set of contiguous IP ports, indicated o IP Port Range: This specifies a set of contiguous IP ports
by the lowest numerical number and the highest numerical number, indicated by the lowest numerical number and the highest numerical
inclusively. number, inclusively.
o Internal IP Address: refers to the IP address that is used by a o Internal IP Address: This refers to the IP address that is used by
host as a source IP address in an outbound IP packet sent towards a host as a source IP address in an outbound IP packet sent
a device supporting port ranges in the internal realm. The towards a device supporting port ranges in the internal realm.
internal IP address may be IPv4 or IPv6. The internal IP address may be IPv4 or IPv6.
o External IP Address: refers to the IP address that is used as a o External IP Address: This refers to the IP address that is used as
source IP address in an outbound IP packet after traversing a a source IP address in an outbound IP packet after traversing a
device supporting port ranges in the external realm. This device supporting port ranges in the external realm. This
document assumes that the external IP address is an IPv4 address. document assumes that the external IP address is an IPv4 address.
o Internal Port: is an IP transport port, which is allocated by a o Internal Port: This is an IP transport port that is allocated by a
host or application behind an address sharing device for an host or application behind an address-sharing device for an
outbound IP packet in the internal realm. outbound IP packet in the internal realm.
o External Port: is an IP transport port, which is allocated by an o External Port: This is an IP transport port that is allocated by
address sharing device upon receiving an outbound IP packet in the an address-sharing device upon receiving an outbound IP packet in
internal realm, and is used to replace the internal port that is the internal realm and is used to replace the internal port that
allocated by a user or application. is allocated by a user or application.
o External realm: refers to the networking segment where external IP o External Realm: This refers to the networking segment where
addresses are used as source addresses of outbound packets external IP addresses are used as source addresses of outbound
forwarded by an address sharing device. packets forwarded by an address-sharing device.
o Internal realm: refers to the networking segment that is behind an o Internal Realm: This refers to the networking segment that is
address sharing device and where internal IP addresses are used. behind an address-sharing device and where internal IP addresses
are used.
o Mapping: denotes a relationship between an internal IP address, o Mapping: This denotes a relationship between an internal IP
internal port and the protocol, and an external IP address, address, internal port, and protocol, as well as an external IP
external port, and the protocol. address, external port, and protocol.
o Address sharing device: a device that is capable of sharing an o Address-Sharing Device: This is a device that is capable of
IPv4 address among multiple users. A typical example of this sharing an IPv4 address among multiple users. A typical example
device is a CGN, CPE, Provider WLAN Gateway, etc. of this device is a CGN, CPE, Provider WLAN gateway, etc.
2.1. Requirements Language
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].
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 subsections:
1. IP-Port-Limit-Info 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 These attributes and their embedded TLVs (refer to Section 3.2) are
defined with globally unique names and follow the guideline in defined with globally unique names and follow the guidelines in
Section 2.7.1 of [RFC6929]. 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 subsections, the fields are transmitted from left to
to right. right.
3.1. Extended Attributes for IP Ports 3.1. Extended Attributes for IP Ports
3.1.1. IP-Port-Limit-Info 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 some sub-attributes and the Extensions [RFC6929]. It contains some sub-attributes, and the
requirement is as follows: requirements are as follows:
o The IP-Port-Limit-Info Attribute MAY contain the IP-Port-Type TLV o The IP-Port-Limit-Info Attribute MAY contain the IP-Port-Type TLV
(see Section 3.2.1). (see Section 3.2.1).
o The IP-Port-Limit-Info Attribute MUST contain the IP-Port-Limit o The IP-Port-Limit-Info Attribute MUST contain the
TLV (see Section 3.2.2). IP-Port-Limit TLV (see Section 3.2.2).
o The IP-Port-Limit-Info Attribute MAY contain the IP-Port-Ext- o The IP-Port-Limit-Info Attribute MAY contain the
IPv4-Addr TLV (see Section 3.2.3). IP-Port-Ext-IPv4-Addr TLV (see Section 3.2.3).
The IP-Port-Limit-Info Attribute specifies the maximum number of IP The IP-Port-Limit-Info Attribute specifies the maximum number of IP
ports as indicated in IP-Port-Limit TLV, of a specific IP transport ports, as indicated in IP-Port-Limit TLV, of a specific IP transport
protocol as indicated in IP-Port-Type TLV, and associated with a protocol, 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 given IPv4 address, as indicated in IP-Port-Ext-IPv4-Addr TLV, for an
end user. end user.
Note that when IP-Port-Type TLV is not included as part of the IP- Note that when IP-Port-Type TLV is not included as part of the
Port-Limit-Info Attribute, the port limit applies to all IP transport IP-Port-Limit-Info Attribute, the port limit applies to all IP
protocols. transport protocols.
Note also that when IP-Port-Ext-IPv4-Addr TLV is not included as part Note also that when IP-Port-Ext-IPv4-Addr TLV is not included as part
of the IP-Port-Limit-Info Attribute, the port limit applies to all of the IP-Port-Limit-Info Attribute, the port limit applies to all
the IPv4 addresses managed by the address sharing device, e.g., a CGN the IPv4 addresses managed by the address-sharing device, e.g., a CGN
or NAT64 device. or NAT64 device.
The IP-Port-Limit-Info Attribute MAY appear in an Access-Accept The IP-Port-Limit-Info Attribute MAY appear in an Access-Accept
packet. It MAY also appear in an Access-Request packet as a packet. It MAY also appear in an Access-Request packet as a
preferred maximum number of IP ports indicated by the device preferred maximum number of IP ports indicated by the device
supporting port ranges co-located with the NAS, e.g., a CGN or NAT64. supporting port ranges co-located with the NAS, e.g., a CGN or NAT64.
The IP-Port-Limit-Info 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-Info Attribute MAY appear in an Accounting-Request The IP-Port-Limit-Info Attribute MAY appear in an Accounting-Request
skipping to change at page 7, line 31 skipping to change at page 8, line 39
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Figure 1 Figure 1
Type Type
241 241
Length Length
This field indicates the total length in bytes of all fields of This field indicates the total length in octets 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
5 5
Value Value
This field contains a set of TLVs as follows: This field contains a set of TLVs as follows:
skipping to change at page 8, line 6 skipping to change at page 9, line 20
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-Info end user. This TLV MUST be included in the IP-Port-Limit-Info
Attribute. Refer to Section 3.2.2. This limit applies to all Attribute. Refer to Section 3.2.2. This limit applies to all
mappings that can be instantiated by an underlying address mappings that can be instantiated by an underlying address-
sharing device without soliciting any external entity. In sharing device without soliciting any external entity. In
particular, this limit does not include the ports that are particular, this limit does not include the ports that are
instructed by an AAA server. instructed by an Authentication, Authorization, and Accounting
(AAA) server.
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-Info optionally included as part of the IP-Port-Limit-Info
Attribute. Refer to Section 3.2.3. Attribute. Refer to Section 3.2.3.
IP-Port-Limit-Info Attribute is associated with the following IP-Port-Limit-Info Attribute is associated with the following
identifier: 241.5. identifier: 241.5.
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 some sub-attributes and the Extensions [RFC6929]. It contains some sub-attributes and the
requirement is as follows: requirement is as follows:
o The IP-Port-Range Attribute MAY contain the IP-Port-Type TLV (see o The IP-Port-Range Attribute MAY contain the IP-Port-Type TLV (see
Section 3.2.1). Section 3.2.1).
o The IP-Port-Range Attribute MUST contain the IP-Port-Alloc TLV o The IP-Port-Range Attribute MUST contain the IP-Port-Alloc TLV
(see Section 3.2.8). (see Section 3.2.8).
o For port allocation, the IP-Port-Range Attribute MUST contain both o For port allocation, the IP-Port-Range Attribute MUST contain both
the IP-Port-Range-Start TLV (see Section 3.2.9) and the IP-Port- the IP-Port-Range-Start TLV (see Section 3.2.9) and the
Range-END TLV (see Section 3.2.10). For port deallocation, the IP-Port-Range-End TLV (see Section 3.2.10). For port
IP-Port-Range Attribute MAY contain both of these two TLVs; if the deallocation, the IP-Port-Range Attribute MAY contain both of
two TLVs are not included, it implies that all ports that were these two TLVs; if the two TLVs are not included, it implies that
previously allocated are now all deallocated. all ports that were previously allocated are now all deallocated.
o The IP-Port-Range Attribute MAY contain the IP-Port-Ext-IPv4-Addr o The IP-Port-Range Attribute MAY contain the
TLV (see Section 3.2.3). IP-Port-Ext-IPv4-Addr TLV (see Section 3.2.3).
o The IP-Port-Range Attribute MAY contain the IP-Port-Local-Id TLV o The IP-Port-Range Attribute MAY contain the IP-Port-Local-Id TLV
(see Section 3.2.11). (see Section 3.2.11).
The IP-Port-Range Attribute contains a range of contiguous IP ports. The IP-Port-Range Attribute contains a range of contiguous IP ports.
These ports are either to be allocated or deallocated depending on These ports are either to be allocated or deallocated depending on
the Value carried by the IP-Port-Alloc TLV. the Value carried by the IP-Port-Alloc TLV.
If the IP-Port-Type TLV is included as part of the IP-Port-Range If the IP-Port-Type TLV is included as part of the IP-Port-Range
Attribute, the port range is associated with the specific IP Attribute, then the port range is associated with the specific IP
transport protocol as specified in the IP-Port-Type TLV, but transport protocol as specified in the IP-Port-Type TLV, but
otherwise is for all IP transport protocols. otherwise it is for all IP transport protocols.
If the IP-Port-Ext-IPv4-Addr TLV is included as part of the IP-Port- If the IP-Port-Ext-IPv4-Addr TLV is included as part of the
Range Attribute, the port range as specified is associated with IPv4 IP-Port-Range Attribute, then the port range as specified is
address as indicated, but otherwise is for all IPv4 addresses by the associated with the IPv4 address as indicated, but otherwise it is
address sharing device (e.g., a CGN device) for the end user. for all IPv4 addresses by the address-sharing device (e.g., a CGN
device) for the end user.
This attribute can be used to convey a single IP transport port This attribute can be used to convey a single IP transport port
number; in such case the Value of the IP-Port-Range-Start TLV and the number: in such case, the Value of the IP-Port-Range-Start TLV and
IP-Port-Range-End TLV, respectively, contain the same port number. the IP-Port-Range-End TLV, respectively, contain the same port
number.
The information contained in the IP-Port-Range Attribute is sent to The information contained in the IP-Port-Range Attribute is sent to
RADIUS server. RADIUS server.
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 is shown in Figure 2. The format of the IP-Port-Range Attribute is shown in Figure 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 | Extended-Type | Value ... | Type | Length | Extended-Type | Value ...
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Figure 2 Figure 2
Type Type
241 241
Length Length
This field indicates the total length in bytes of all fields of This field indicates the total length in octets 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
6 6
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 the range of the specified
specified IP ports for either allocation or deallocation. This IP ports for either allocation or deallocation. This TLV MUST
TLV MUST be included as part of the IP-Port-Range Attribute. be included as part of the IP-Port-Range Attribute. Refer to
Refer to Section 3.2.8. 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 is collectively indicated in the
Start TLV and the IP-Port-Range-End TLV. This TLV is IP-Port-Range-Start TLV and the IP-Port-Range-End TLV. This
optionally included as part of the IP-Port-Range Attribute. TLV is optionally included as part of the IP-Port-Range
Refer to Section 3.2.3. Attribute. 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 significant identifier at the
premise, such as MAC address, interface ID, VLAN ID, PPP customer premise, such as the Media Access Control (MAC)
sessions ID, VRF ID, IP address/prefix, etc. This TLV is address, interface ID, VLAN ID, PPP sessions ID, VPN Routing
and Forwarding (VRF) ID, IP 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.6. identifier: 241.6.
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 some sub-attributes and the Extensions [RFC6929]. It contains some sub-attributes and the
requirement is as follows: requirement is as follows:
o The IP-Port-Forwarding-Map Attribute MAY contain the IP-Port-Type o The IP-Port-Forwarding-Map Attribute MAY contain the
TLV (see Section 3.2.1). IP-Port-Type TLV (see Section 3.2.1).
o The IP-Port-Forwarding-Map Attribute MUST contain both IP-Port- o The IP-Port-Forwarding-Map Attribute MUST contain both
Int-Port TLV (see Section 3.2.6) and the IP-Port-Ext-Port TLV (see IP-Port-Int-Port TLV (see Section 3.2.6) and the
Section 3.2.7). IP-Port-Ext-Port TLV (see Section 3.2.7).
o If the internal realm is with IPv4 address family, the IP-Port- o If the internal realm is with an IPv4 address family, the
Forwarding-Map Attribute MUST contain the IP-Port-Int-IPv4-Addr IP-Port-Forwarding-Map Attribute MUST contain the
TLV (see Section 3.2.4); if the internal realm is with IPv6 IP-Port-Int-IPv4-Addr TLV (see Section 3.2.4); if the internal
address family, the IP-Port-Forwarding-Map Attribute MUST contain realm is with an IPv6 address family, the IP-Port-Forwarding-Map
the IP-Port-Int-IPv6-Addr TLV (see Section 3.2.5). Attribute MUST contain the IP-Port-Int-IPv6-Addr TLV (see
Section 3.2.5).
o The IP-Port-Forwarding-Map Attribute MAY contain the IP-Port-Ext- o The IP-Port-Forwarding-Map Attribute MAY contain the
IPv4-Addr TLV (see Section 3.2.3). IP-Port-Ext-IPv4-Addr TLV (see Section 3.2.3).
o The IP-Port-Forwarding-Map Attribute MAY contain the IP-Port- o The IP-Port-Forwarding-Map Attribute MAY contain the
Local-Id TLV (see Section 3.2.11). IP-Port-Local-Id TLV (see Section 3.2.11).
The attribute contains a 2-byte IP internal port number and a 2-byte The attribute contains a two-octet IP internal port number and a
IP external port number. The internal port number is associated with two-octet IP external port number. The internal port number is
an internal IPv4 or IPv6 address that MUST always be included. The associated with an internal IPv4 or IPv6 address that MUST always be
external port number is associated with a specific external IPv4 included. The external port number is associated with a specific
address if included, but otherwise with all external IPv4 addresses external IPv4 address if included, but otherwise it is associated
for the end user. with all external IPv4 addresses for the end user.
If the IP-Port-Type TLV is included as part of the IP-Port- If the IP-Port-Type TLV is included as part of the
Forwarding-Map Attribute, the port mapping is associated with the IP-Port-Forwarding-Map Attribute, then the port mapping is associated
specific IP transport protocol as specified in the IP-Port-Type TLV, with the specific IP transport protocol as specified in the
but otherwise is for all IP transport protocols. IP-Port-Type TLV, but otherwise it is for all IP transport protocols.
The IP-Port-Forwarding-Map Attribute MAY appear in an Access-Accept The IP-Port-Forwarding-Map Attribute MAY appear in an Access-Accept
packet. It MAY also appear in an Access-Request packet to indicate a packet. It MAY also appear in an Access-Request packet to indicate a
preferred port mapping by the device co-located with NAS. However preferred port mapping by the device co-located with NAS. However,
the server is not required to honor such a preference. the server is not required to honor such a preference.
The IP-Port-Forwarding-Map Attribute MAY appear in a CoA-Request The IP-Port-Forwarding-Map Attribute MAY appear in a CoA-Request
packet. packet.
The IP-Port-Forwarding-Map Attribute MAY also appear in an The IP-Port-Forwarding-Map Attribute MAY also appear in an
Accounting-Request packet. Accounting-Request packet.
The IP-Port-Forwarding-Map Attribute MUST NOT appear in any other The IP-Port-Forwarding-Map Attribute MUST NOT appear in any other
RADIUS packet. RADIUS packet.
skipping to change at page 12, line 25 skipping to change at page 14, line 22
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Figure 3 Figure 3
Type Type
241 241
Length Length
This field indicates the total length in bytes of all fields of This field indicates the total length in octets 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
7 7
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
Forwarding-Map attribute. Refer to Section 3.2.6. IP-Port-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 internal realm with IPv4 address family, this TLV MUST be For the internal realm with an IPv4 address family, this TLV
included as part of the IP-Port-Forwarding-Map Attribute. MUST be included as part of the IP-Port-Forwarding-Map
Refer to Section 3.2.4. Attribute. Refer to Section 3.2.4.
IP-Port-Int-IPv6-Addr TLV IP-Port-Int-IPv6-Addr TLV
This TLV contains an IPv6 address that is associated with the This TLV contains an IPv6 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 internal realm with IPv6 address family, this TLV MUST be For the internal realm with an IPv6 address family, this TLV
included as part of the IP-Port-Forwarding-Map Attribute. MUST be included as part of the IP-Port-Forwarding-Map
Refer to Section 3.2.5. Attribute. Refer to Section 3.2.5.
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.
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 significant identifier at the
premise, such as MAC address, interface ID, VLAN ID, PPP customer premise, such as MAC address, interface ID, VLAN ID,
sessions ID, VRF ID, IP address/prefix, etc. This TLV is PPP sessions ID, VRF ID, IP address/prefix, etc. This TLV is
optionally included as part of the IP-Port-Forwarding-Map optionally included as part of the IP-Port-Forwarding-Map
Attribute. Refer to Section 3.2.11. Attribute. Refer to Section 3.2.11.
The IP-Port-Forwarding-Map Attribute is associated with the following The IP-Port-Forwarding-Map Attribute is associated with the following
identifier: 241.7. identifier: 241.7.
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) 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 are defined in the following subsections. These TLVs use the format
defined in [RFC6929]. As the three attributes carry similar data, we defined in [RFC6929]. As the three attributes carry similar data, we
have defined a common set of TLVs which are used for all three have defined a common set of TLVs that are used for all three
attributes. That is, the TLVs have the same name and number, when attributes. That is, the TLVs have the same name and number when
encapsulated in any one of the three parent attributes. See encapsulated in any one of the three parent attributes. See
Section 3.1.1, Section 3.1.2, and Section 3.1.3 for a list of which Sections 3.1.1, 3.1.2, and 3.1.3 for a list of which TLV is permitted
TLV is permitted within which parent attribute. within which parent attribute.
The encoding of the Value field of these TLVs follows the The encoding of the Value field of these TLVs follows the
recommendation of [RFC6158]. In particular, IP-Port-Type, IP-Port- recommendation of [RFC6158]. In particular, IP-Port-Type,
Limit, IP-Port-Int-Port, IP-Port-Ext-Port, IP-Port-Alloc, IP-Port- IP-Port-Limit, IP-Port-Int-Port, IP-Port-Ext-Port, IP-Port-Alloc,
Range-Start, and IP-Port-Range-End TLVs are encoded in 32 bits as per IP-Port-Range-Start, and IP-Port-Range-End TLVs are encoded in
the recommendation in Appendix A.2.1 of [RFC6158]. 32 bits as per the recommendation in Appendix A.2.1 of [RFC6158].
3.2.1. IP-Port-Type TLV 3.2.1. IP-Port-Type TLV
The format of IP-Port-Type TLV is shown in Figure 4. This attribute The format of IP-Port-Type TLV is shown in Figure 4. This attribute
carries the IP transport protocol number defined by IANA (refer to carries the IP transport protocol number defined by IANA (refer to
[ProtocolNumbers]) [ProtocolNumbers]).
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
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| TLV-Type | Length | Protocol-Number | TLV-Type | Length | Protocol-Number
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Protocol-Number | Protocol-Number |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Figure 4 Figure 4
TLV-Type TLV-Type
1 1
Length Length
6 Six octets
Protocol-Number Protocol-Number
Integer. This field contains the data (unsigned8) of the protocol Integer. This field contains the data (unsigned8) of the protocol
number defined in [ProtocolNumbers], right justified, and the number defined in [ProtocolNumbers], right justified, and the
unused bits in this field MUST be set to zero. Protocols that do unused bits in this field MUST be set to zero. Protocols that do
not use a port number (e.g., Resource Reservation Protocol (RSVP), not use a port number (e.g., the Resource Reservation Protocol
IP Encapsulating Security Payload (ESP)) MUST NOT be included in (RSVP) or IP Encapsulating Security Payload (ESP)) MUST NOT be
the IP-Port-Type TLV. included in the IP-Port-Type TLV.
IP-Port-Type TLV MAY be included in the following Attributes: IP-Port-Type TLV MAY be included in the following attributes:
o IP-Port-Limit-Info Attribute, identified as 241.5.1 (see o IP-Port-Limit-Info Attribute, identified as 241.5.1 (see
Section 3.1.1). Section 3.1.1)
o IP-Port-Range Attribute, identified as 241.6.1 (see o IP-Port-Range Attribute, identified as 241.6.1 (see Section 3.1.2)
Section 3.1.2).
o IP-Port-Forwarding-Map Attribute, identified as 241.7.1 (see o IP-Port-Forwarding-Map Attribute, identified as 241.7.1 (see
Section 3.1.3). Section 3.1.3)
When the IP-Port-Type TLV is included within a RADIUS Attribute, the When the IP-Port-Type TLV is included within a RADIUS attribute, the
associated attribute is applied to the IP transport protocol as associated attribute is applied to the IP transport protocol as
indicated by the Protocol-Number only, such as TCP, UDP, SCTP, DCCP, indicated by the Protocol-Number only, such as TCP, UDP, SCTP,
etc. DCCP, etc.
3.2.2. IP-Port-Limit TLV 3.2.2. IP-Port-Limit TLV
The format of IP-Port-Limit TLV is shown in Figure 5. This attribute The format of IP-Port-Limit TLV is shown in Figure 5. This attribute
carries IPFIX Information Element "sourceTransportPortsLimit (458), carries IPFIX Information Element 458, "sourceTransportPortsLimit",
which indicates the maximum number of IP transport ports as a limit which indicates the maximum number of IP transport ports as a limit
for an end user to use that is associated with one or more IPv4 or for an end user to use that is associated with one or more IPv4 or
IPv6 addresses. IPv6 addresses.
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
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| TLV-Type | Length | sourceTransportPortsLimit | TLV-Type | Length | sourceTransportPortsLimit
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
sourceTransportPortsLimit | sourceTransportPortsLimit |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Figure 5 Figure 5
TLV-Type TLV-Type
2 2
Length Length
6 Six octets
sourceTransportPortsLimit sourceTransportPortsLimit
Integer. This field contains the data (unsigned16) of Integer. This field contains the data (unsigned16) of
sourceTransportPortsLimit (458) defined in IPFIX, right justified, sourceTransportPortsLimit (458) defined in IPFIX, right justified,
and the unused bits in this field MUST be set to zero. and the unused bits in this field MUST be set to zero.
IP-Port-Limit TLV MUST be included as part of the IP-Port-Limit-Info IP-Port-Limit TLV MUST be included as part of the IP-Port-Limit-Info
Attribute (refer to Section 3.1.1), identified as 241.5.2. Attribute (refer to Section 3.1.1), identified as 241.5.2.
skipping to change at page 16, line 28 skipping to change at page 18, line 28
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Figure 6 Figure 6
TLV-Type TLV-Type
3 3
Length Length
6 Six octets
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 IP-Port-Ext-IPv4-Addr TLV MAY be included in the following
Attributes: attributes:
o IP-Port-Limit-Info Attribute, identified as 241.5.3 (see o IP-Port-Limit-Info Attribute, identified as 241.5.3 (see
Section 3.1.1). Section 3.1.1)
o IP-Port-Range Attribute, identified as 241.6.3 (see o IP-Port-Range Attribute, identified as 241.6.3 (see Section 3.1.2)
Section 3.1.2).
o IP-Port-Forwarding-Mapping Attribute, identified as 241.7.3 (see o IP-Port-Forwarding-Mapping Attribute, identified as 241.7.3 (see
Section 3.1.3). Section 3.1.3)
3.2.4. IP-Port-Int-IPv4-Addr TLV 3.2.4. IP-Port-Int-IPv4-Addr TLV
The format of IP-Port-Int-IPv4 TLV is shown in Figure 7. This The format of IP-Port-Int-IPv4 TLV is shown in Figure 7. This
attribute carries IPFIX Information Element 8, "sourceIPv4Address", attribute carries IPFIX Information Element 8, "sourceIPv4Address",
which is the IPv4 source address before NAT operation (refer to which is the IPv4 source address before NAT operation (refer to
[IPFIX]). [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
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| TLV-Type | Length | sourceIPv4Address | TLV-Type | Length | sourceIPv4Address
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
sourceIPv4Address | sourceIPv4Address |
+-+--+-+-+-+-+-+-++-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Figure 7 Figure 7
TLV-Type TLV-Type
4 4
Length Length
6 Six octets
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.
If the internal realm is with IPv4 address family, the IP-Port-Int- If the internal realm is with an IPv4 address family, the
IPv4-Addr TLV MUST be included as part of the IP-Port-Forwarding-Map IP-Port-Int-IPv4-Addr TLV MUST be included as part of the
Attribute (refer to Section 3.1.3), identified as 241.7.4. IP-Port-Forwarding-Map Attribute (refer to Section 3.1.3),
identified as 241.7.4.
3.2.5. IP-Port-Int-IPv6-Addr TLV 3.2.5. IP-Port-Int-IPv6-Addr TLV
The format of IP-Port-Int-IPv6-Addr TLV is shown in Figure 8. This The format of IP-Port-Int-IPv6-Addr TLV is shown in Figure 8. This
attribute carries IPFIX Information Element 27, "sourceIPv6Address", attribute carries IPFIX Information Element 27, "sourceIPv6Address",
which is the IPv6 source address before NAT operation (refer to which is the IPv6 source address before NAT operation (refer to
[IPFIX]). [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
skipping to change at page 18, line 27 skipping to change at page 20, line 34
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Figure 8 Figure 8
TLV-Type TLV-Type
5 5
Length Length
18 Eighteen octets
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.
If the internal realm is with IPv6 address family, the IP-Port-Int- If the internal realm is with an IPv6 address family, the
IPv6-Addr TLV MUST be included as part of the IP-Port-Forwarding-Map IP-Port-Int-IPv6-Addr TLV MUST be included as part of the
Attribute (refer to Section 3.1.3), identified as 241.7.5. IP-Port-Forwarding-Map Attribute (refer to Section 3.1.3),
identified as 241.7.5.
3.2.6. IP-Port-Int-Port TLV 3.2.6. IP-Port-Int-Port TLV
The format of IP-Port-Int-Port TLV is shown in Figure 9. This The format of IP-Port-Int-Port TLV is shown in Figure 9. This
attribute carries IPFIX Information Element 7, "sourceTransportPort", attribute carries IPFIX Information Element 7, "sourceTransportPort",
which is the source transport number associated with an internal IPv4 which is the source transport number associated with an internal IPv4
or IPv6 address (refer to [IPFIX]). or IPv6 address (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
skipping to change at page 19, line 21 skipping to change at page 21, line 28
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Figure 9 Figure 9
TLV-Type TLV-Type
6 6
Length Length
6 Six octets
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 sourceTransportPort (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 MUST be included as part of the IP-Port- IP-Port-Int-Port TLV MUST be included as part of the
Forwarding-Map Attribute (refer to Section 3.1.3), identified as IP-Port-Forwarding-Map Attribute (refer to Section 3.1.3),
241.7.6. identified as 241.7.6.
3.2.7. IP-Port-Ext-Port TLV 3.2.7. IP-Port-Ext-Port TLV
The format of IP-Port-Ext-Port TLV is shown in Figure 10. This The format of IP-Port-Ext-Port TLV is shown in Figure 10. This
attribute carries IPFIX Information Element 227, attribute carries IPFIX Information Element 227,
"postNAPTSourceTransportPort", which is the transport number "postNAPTSourceTransportPort", which is the transport number
associated with an external IPv4 address(refer to [IPFIX]). associated with an external IPv4 address (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
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| TLV-Type | Length | postNAPTSourceTransportPort | TLV-Type | Length | postNAPTSourceTransportPort
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
postNAPTSourceTransportPort | postNAPTSourceTransportPort |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Figure 10 Figure 10
skipping to change at page 20, line 4 skipping to change at page 22, line 23
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
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| TLV-Type | Length | postNAPTSourceTransportPort | TLV-Type | Length | postNAPTSourceTransportPort
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
postNAPTSourceTransportPort | postNAPTSourceTransportPort |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Figure 10 Figure 10
TLV-Type TLV-Type
7 7
Length Length
6 Six octets
postNAPTSourceTransportPort postNAPTSourceTransportPort
Integer. This field contains the data (unsigned16) of Integer. This field contains the data (unsigned16) of
postNAPTSourceTrasnportPort (227) defined in IPFIX, right postNAPTSourceTransportPort (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 MUST be included as part of the IP-Port- IP-Port-Ext-Port TLV MUST be included as part of the
Forwarding-Map Attribute (refer to Section 3.1.3), identified as IP-Port-Forwarding-Map Attribute (refer to Section 3.1.3),
241.7.7. identified as 241.7.7.
3.2.8. IP-Port-Alloc TLV 3.2.8. IP-Port-Alloc TLV
The format of IP-Port-Alloc TLV is shown in Figure 11. This The format of IP-Port-Alloc TLV is shown in Figure 11. This
attribute carries IPFIX Information Element 230, "natEvent", which is attribute carries IPFIX Information Element 230, "natEvent", which is
a flag to indicate an action of NAT operation (refer to [IPFIX]). a flag to indicate an action 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 deallocate a range of transports ports. For the purpose of this to deallocate a range of transports ports. For the purpose of this
skipping to change at page 20, line 47 skipping to change at page 23, line 32
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Figure 11 Figure 11
TLV-Type TLV-Type
8 8
Length Length
6 Six octets
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: 0: Reserved
1: Allocation
Allocation 2: Deallocation
2:
Deallocation
Reserved:
0.
IP-Port-Alloc TLV MUST be included as part of the IP-Port-Range IP-Port-Alloc TLV MUST be included as part of the IP-Port-Range
Attribute (refer to Section 3.1.2), identified as 241.6.8. Attribute (refer to Section 3.1.2), identified as 241.6.8.
3.2.9. IP-Port-Range-Start TLV 3.2.9. IP-Port-Range-Start TLV
The format of IP-Port-Range-Start TLV is shown in Figure 12. This The format of IP-Port-Range-Start TLV is shown in Figure 12. This
attribute carries IPFIX Information Element 361, "portRangeStart", attribute carries IPFIX Information Element 361, "portRangeStart",
which is the smallest port number of a range of contiguous transport which is the smallest port number of a range of contiguous transport
ports (refer to [IPFIX]). ports (refer to [IPFIX]).
skipping to change at page 21, line 47 skipping to change at page 24, line 28
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Figure 12 Figure 12
TLV-Type TLV-Type
9 9
Length Length
6 Six octets
portRangeStart portRangeStart
Integer. This field contains the data (unsigned16) of (361)
defined in IPFIX, right justified, and unused bits MUST be set to Integer. This field contains the data (unsigned16) of
zero. portRangeStart (361) defined in IPFIX, right justified, and unused
bits MUST be set to zero.
IP-Port-Range-Start TLV is included as part of the IP-Port-Range IP-Port-Range-Start TLV is included as part of the IP-Port-Range
Attribute (refer to Section 3.1.2), identified as 241.6.9. Attribute (refer to Section 3.1.2), identified as 241.6.9.
3.2.10. IP-Port-Range-End TLV 3.2.10. IP-Port-Range-End TLV
The format of IP-Port-Range-End TLV is shown in Figure 13. This The format of IP-Port-Range-End TLV is shown in Figure 13. This
attribute carries IPFIX Information Element 362, "portRangeEnd", attribute carries IPFIX Information Element 362, "portRangeEnd",
which is the largest port number of a range of contiguous transport which is the largest port number of a range of contiguous transport
ports (refer to [IPFIX]). ports (refer to [IPFIX]).
skipping to change at page 22, line 34 skipping to change at page 25, line 28
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Figure 13 Figure 13
TLV-Type TLV-Type
10 10
Length Length
6 Six octets
portRangeEnd portRangeEnd
Integer. This field contains the data (unsigned16) of (362) Integer. This field contains the data (unsigned16) of
defined in IPFIX, right justified, and unused bits MUST be set to portRangeEnd (362) defined in IPFIX, right justified, and unused
zero. bits MUST be set to zero.
IP-Port-Range-End TLV is included as part of the IP-Port-Range IP-Port-Range-End TLV is included as part of the IP-Port-Range
Attribute (refer to Section 3.1.2), identified as 241.6.10. Attribute (refer to Section 3.1.2), identified as 241.6.10.
3.2.11. IP-Port-Local-Id TLV 3.2.11. IP-Port-Local-Id TLV
The format of IP-Port-Local-Id TLV is shown in Figure 14. This The format of IP-Port-Local-Id TLV is shown in Figure 14. This
attribute carries a string called "localID", which is a local attribute carries a string called "localID", which is a local
significant identifier as explained below. significant identifier as explained below.
The primary issue addressed by this TLV is that there are CGN The primary issue addressed by this TLV is that there are CGN
deployments that do not distinguish internal hosts by their internal deployments that do not distinguish internal hosts by their internal
IP address alone, but use further identifiers for unique subscriber IP address alone but use further identifiers for unique subscriber
identification. For example, this is the case if a CGN supports identification. For example, this is the case if a CGN supports
overlapping private or shared IP address spaces (refer to [RFC1918] overlapping private or shared IP address spaces (as described in
and [RFC6598]) for internal hosts of different subscribers. In such [RFC1918] and [RFC6598]) for internal hosts of different subscribers.
cases, different internal hosts are identified and mapped at the CGN In such cases, different internal hosts are identified and mapped at
by their IP address and/or another identifier, for example, the the CGN by their IP address and/or another identifier, for example,
identifier of a tunnel between the CGN and the subscriber. In these the identifier of a tunnel between the CGN and the subscriber. In
scenarios (and similar ones), the internal IP address is not these scenarios (and similar ones), the internal IP address is not
sufficient to demultiplex connections from internal hosts. An sufficient to demultiplex connections from internal hosts. An
additional identifier needs to be present in the IP-Port-Range additional identifier needs to be present in the IP-Port-Range
Attribute and IP-Port-Forwarding-Mapping Attribute in order to Attribute and IP-Port-Forwarding-Mapping Attribute in order to
uniquely identify an internal host. The IP-Port-Local-Id TLV is used uniquely identify an internal host. The IP-Port-Local-Id TLV is used
to carry this identifier. to carry this identifier.
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
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| TLV-Type | Length | localID .... | TLV-Type | Length | localID ....
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Figure 14 Figure 14
TLV-Type TLV-Type
11 11
Length Length
Variable number of bytes. Variable number of octets
localID localID
string. The data type of this field is string (refer to String. The data type of this field is string (refer to
[I-D.ietf-radext-datatypes]). This field contains the data that [RFC8044]). This field contains the data that is a local
is a local session identifier at the customer premise, such as MAC significant identifier at the customer premise, such as MAC
address, interface ID, VLAN ID, PPP sessions ID, VRF ID, IP address, interface ID, VLAN ID, PPP sessions ID, VRF ID, IP
address/prefix, or another local session identifier. address/prefix, or another local significant identifier.
IP-Port-Local-Id TLV MAY be included in the following Attributes if IP-Port-Local-Id TLV MAY be included in the following Attributes if
it is necessary to identify the subscriber: it is necessary to identify the subscriber:
o IP-Port-Range Attribute, identified as 241.6.11 (see o IP-Port-Range Attribute, identified as 241.6.11 (see
Section 3.1.2). Section 3.1.2)
o IP-Port-Forwarding-Mapping Attribute, identified as 241.7.11 (see o IP-Port-Forwarding-Mapping Attribute, identified as 241.7.11 (see
Section 3.1.3). 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
to the Internet service, where either PPP or DHCP/DHCPv6 is used. 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 When a user signs in, the NAS sends a RADIUS Access-Request message
to the RADIUS server. The RADIUS server validates the request, and to the RADIUS server. The RADIUS server validates the request, and
if the validation succeeds, it in turn sends back a RADIUS Access- if the validation succeeds, it in turn sends back a RADIUS
Accept message. The Access-Accept message carries configuration Access-Accept message. The Access-Accept message carries
information specific to that user, back to the NAS, where some of the configuration information specific to that user back to the NAS,
information would pass on to the requesting user via PPP or DHCP/ where some of the information would be passed on to the requesting
DHCPv6. user via PPP or DHCP/DHCPv6.
A CGN function in a broadband network is most likely be co-located on A CGN function in a broadband network is most likely to be co-located
a BNG. In that case, parameters for CGN port mapping behavior for on a BNG. In that case, parameters for CGN port mapping behavior for
users can be configured on the RADIUS server. When a user signs in users can be configured on the RADIUS server. When a user signs in
to the Internet service, the associated parameters can be conveyed to to the Internet service, the associated parameters can be conveyed to
the NAS, and proper configuration is accomplished on the CGN device the NAS, and proper configuration is accomplished on the CGN device
for that user. for that user.
Also, CGN operation status such as CGN port allocation and Also, a CGN operation status such as CGN port allocation and
deallocation 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 purposes using the RADIUS
protocol. protocol.
RADIUS protocol has already been widely deployed in broadband The 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 subsections, we describe how to manage CGN behavior
using RADIUS protocol, with required RADIUS extensions proposed in using the RADIUS protocol, with required RADIUS extensions proposed
Section 3. in Section 3.
4.1.1. Configure IP Port Limit for a User 4.1.1. Configure IP Port Limit for a User
In the face of IPv4 address shortage, there are currently proposals In the face of an IPv4 address shortage, there are currently
to multiplex multiple users' connections over a number of shared IPv4 proposals to multiplex multiple users' connections over a number of
addresses, such as Carrier Grade NAT [RFC6888], Dual-Stack Lite shared IPv4 addresses, such as Carrier Grade NAT [RFC6888],
Dual-Stack Lite [RFC6333], NAT64 [RFC6146], etc. As a result, a
[RFC6333], NAT64 [RFC6146], etc. As a result, a single IPv4 public single IPv4 public address may be shared by hundreds or even
address may be shared by hundreds or even thousands of users. As thousands of users. As indicated in [RFC6269], it is therefore
indicated in [RFC6269], it is therefore necessary to impose limits on necessary to impose limits on the total number of ports available to
the total number of ports available to an individual user to ensure an individual user to ensure that the shared resource, i.e., the
that the shared resource, i.e., the IPv4 address, remains available IPv4 address, remains available in some capacity to all the users
in some capacity to all the users using it. The support of IP port using it. The support of an IP port limit is also documented in
limit is also documented in [RFC6888] as a requirement for CGN. [RFC6888] as a requirement for CGN.
The IP port limit imposed to an end user may be on the total number The IP port limit imposed on an end user may be on the total number
of IP source transport ports, or a specific IP transport protocol as of IP source transport ports or a specific IP transport protocol as
defined in Section 3.1.1. defined in Section 3.1.1.
The per-user based IP port limit is configured on a RADIUS server, The per-user IP port limit is configured on a RADIUS server, along
along with other user information such as credentials. with other user information such as credentials.
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 the IP-Port- BNG, which is acting as a NAS and is co-located with the CGN using
Limit-Info RADIUS attribute (defined in Section 3.1.1), along with the IP-Port-Limit-Info RADIUS attribute (defined in Section 3.1.1)
other configuration parameters. While some parameters are passed to along 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 IP transport ports for that user. for imposing the usage of IP transport ports for that user.
Figure 15 illustrates how RADIUS protocol is used to configure the Figure 15 illustrates how the RADIUS protocol is used to configure
maximum number of TCP/UDP ports for a given user on a CGN device. the maximum number of TCP/UDP ports for a given user on a CGN device.
User CGN/NAS AAA User CGN/NAS AAA
| BNG Server | BNG Server
| | | | | |
| | | | | |
|----Service Request------>| | |----Service Request------>| |
| | | | | |
| |-----Access-Request -------->| | |-----Access-Request -------->|
| | | | | |
| |<----Access-Accept-----------| | |<----Access-Accept-----------|
skipping to change at page 26, line 5 skipping to change at page 29, line 5
|<---Service Granted ------| | |<---Service Granted ------| |
| (other parameters) | | | (other parameters) | |
| | | | | |
| (CGN external port | | (CGN external port |
| allocation and | | allocation and |
| IPv4 address assignment) | | IPv4 address assignment) |
| | | | | |
Figure 15: RADIUS Message Flow for Configuring CGN Port Limit Figure 15: RADIUS Message Flow for Configuring CGN Port Limit
The IP port limit created on a CGN device for a specific user using The IP port limit created on a CGN device for a specific user using a
RADIUS extension may be changed using RADIUS CoA message [RFC5176] RADIUS extension may be changed using a RADIUS CoA message [RFC5176]
that carries the same RADIUS attribute. The CoA message may be sent that carries the same RADIUS attribute. The CoA message may be sent
from the RADIUS server directly to the NAS, which once accepts and from the RADIUS server directly to the NAS, and once a RADIUS CoA ACK
sends back a RADIUS CoA ACK message, the new IP port limit replaces message is accepted and sent back, the new IP port limit replaces the
the previous one. previous one.
Figure 16 illustrates how RADIUS protocol is used to increase the Figure 16 illustrates how the RADIUS protocol is used to increase the
TCP/UDP port limit from 1024 to 2048 on a CGN device for a specific TCP/UDP port limit from 1024 to 2048 on a CGN device for a specific
user. user.
User CGN/NAS AAA User CGN/NAS AAA
| BNG Server | BNG Server
| | | | | |
| TCP/UDP Port Limit (1024) | | TCP/UDP Port Limit (1024) |
| | | | | |
| |<---------CoA Request----------| | |<---------CoA Request----------|
| | (IP-Port-Limit-Info) | | | (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 CGN port limit Figure 16: RADIUS Message Flow for Changing a User's CGN Port Limit
4.1.2. Report IP Port Allocation/Deallocation 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 an IP transport port for the user when receiving a new IP allocate an IP transport port for the user when receiving a new IP
flow sent from that user. flow sent from that user.
As one practice, a CGN may allocate a block of IP ports for a As one practice, a CGN may allocate a block of IP ports for a
specific user, instead of one port at a time, and within each port specific user, instead of one port at a time, and within each port
block, the ports may be randomly distributed or in consecutive block the ports may be randomly distributed or in consecutive
fashion. When a CGN device allocates a block of transport ports, the fashion. When a CGN device allocates a block of transport ports, the
information can be easily conveyed to the RADIUS server by a new 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). RADIUS attribute called the IP-Port-Range (defined in Section 3.1.2).
The CGN device may allocate one or more IP port ranges, where each The CGN device may allocate one or more IP port ranges, where each
range contains a set of numbers representing IP transport ports, and range contains a set of numbers representing IP transport ports and
the total number of ports MUST be less or equal to the associated IP the total number of ports MUST be less or equal to the associated IP
port limit imposed for that user. A CGN device may choose to port limit imposed for that user. A CGN device may choose to
allocate a small port range, and allocate more at a later time as allocate a small port range and allocate more at a later time as
needed; such practice is good because its randomization in nature. needed; such practice is good because of its randomization in nature.
At the same time, the CGN device also needs to decide the shared IPv4 At the same time, the CGN device also needs to decide on the shared
address for that user. The shared IPv4 address and the pre-allocated IPv4 address for that user. The shared IPv4 address and the
IP port range are both passed to the RADIUS server. pre-allocated IP port range are both passed to the RADIUS server.
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
transport port number from the associated and pre-allocated IP port transport port number from the associated and pre-allocated IP port
range for that user to replace the original source port number, along range for that user to replace the original source port number along
with the replacement of the source IP address by the shared IPv4 with the replacement of the source IP address by the shared IPv4
address. address.
A CGN device may decide to "free" a previously assigned set of IP A CGN device may decide to "free" a previously assigned set of IP
ports that have been allocated for a specific user but not currently ports that have been allocated for a specific user but are not
in use, and with that, the CGN device must send the information of currently in use, and with that, the CGN device must send the
the deallocated IP port range along with the shared IPv4 address to information of the deallocated IP port range along with the shared
the RADIUS server. IPv4 address to the RADIUS server.
Figure 17 illustrates how RADIUS protocol is used to report a set of Figure 17 illustrates how the RADIUS protocol is used to report a set
ports allocated and deallocated, respectively, by a NAT64 device for of ports allocated and deallocated, respectively, by a NAT64 device
a specific user to the RADIUS server. 2001:db8:100:200::/56 is the for a specific user to the RADIUS server. 2001:db8:100:200::/56 is
IPv6 prefix allocated to this user. In order to limit the usage of the IPv6 prefix allocated to this user. In order to limit the usage
the NAT64 resources on a per-user basis for fairness of resource of the NAT64 resources on a per-user basis for fairness of resource
usage (see REQ-4 of [RFC6888]), port range allocations are bound to usage (see REQ-4 of [RFC6888]), port range allocations are bound to
the /56 prefix, not to the source IPv6 address of the request. The the /56 prefix, not to the source IPv6 address of the request. The
NAT64 devices is configured with the per-user port limit policy by NAT64 device is configured with the per-user port limit policy by
some means (e.g., subscriber-mask [RFC7785]). some means (e.g., subscriber-mask [RFC7785]).
Host NAT64/NAS AAA Host NAT64/NAS AAA
| BNG Server | BNG Server
| | | | | |
| | | | | |
|----Service Request------>| | |----Service Request------>| |
| | | | | |
| |-----Access-Request -------->| | |-----Access-Request -------->|
| | | | | |
skipping to change at page 28, line 35 skipping to change at page 31, line 35
... ... ... ... ... ...
| | | | | |
| (NAT64 decides to deallocate | | (NAT64 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 deallocation) | | | for deallocation) |
| | | | | |
Figure 17: RADIUS Message Flow for reporting NAT64 allocation/ Figure 17: RADIUS Message Flow for Reporting NAT64
deallocation of a port set Allocation/Deallocation of a Port Set
4.1.3. Configure Forwarding Port Mapping 4.1.3. Configure Port Forwarding 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
defined allowing IP packets of applications from outside a CGN device pre-defined and allow IP packets of applications from outside a CGN
to pass through and "port forwarded" to the correct user located device to pass through and be "port forwarded" to the correct user
behind the CGN device. located behind the CGN device.
Port Control Protocol [RFC6887], provides a mechanism to create a The Port Control Protocol (PCP) [RFC6887], provides a mechanism to
mapping from an external IP address and port to an internal IP create a mapping from an external IP address and port to an internal
address and port on a CGN device just to achieve the "port IP address and port on a CGN device just to achieve the "port
forwarding" purpose. PCP is a server-client protocol capable of forwarding" purpose. PCP is a server-client protocol capable of
creating or deleting a mapping along with a rich set of features on a 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 CGN device in dynamic fashion. In some deployments, all users need
a few, typically just one pre-configured port mapping for is a few (typically just one) pre-configured port mappings for
applications such as web cam at home, and the lifetime of such a port applications at home, such as a web cam; the lifetime of such a port
mapping remains valid throughout the duration of the customer's mapping remains valid throughout the duration of the customer's
Internet service connection time. In such an environment, it is Internet service connection time. In such an environment, it is
possible to statically configure a port mapping on the RADIUS server possible to statically configure a port mapping on the RADIUS server
for a user and let the RADIUS protocol to propagate the information for a user and let the RADIUS protocol propagate the information to
to the associated CGN device. the associated CGN device.
Note that this document targets deployments where a AAA server is Note that this document targets deployments where a AAA server is
responsible de instructing NAT mappings for a given subscriber and responsible for instructing NAT mappings for a given subscriber and
does not make any assumption about the host's capabilities with does not make any assumption about the host's capabilities with
regards to port forwarding control. This deployment is complementary regards to port forwarding control. This deployment is complementary
to PCP given that PCP targets a different deployment model where an to PCP given that PCP targets a different deployment model where an
application (on the host) controls its mappings in an upstream CPE, application (on the host) controls its mappings in an upstream CPE,
CGN, firewall, etc. CGN, firewall, etc.
Figure 18 illustrates how RADIUS protocol is used to configure a Figure 18 illustrates how the RADIUS protocol is used to configure a
forwarding port mapping on a NAT44 device by using RADIUS protocol. port forwarding mapping on a NAT44 device.
Host CGN/NAS AAA Host CGN/NAS AAA
| BNG Server | BNG Server
| | | | | |
|----Service Request------>| | |----Service Request------>| |
| | | | | |
| |---------Access-Request------->| | |---------Access-Request------->|
| | | | | |
| |<--------Access-Accept---------| | |<--------Access-Accept---------|
| | (IP-Port-Forwarding-Map) | | | (IP-Port-Forwarding-Map) |
skipping to change at page 29, line 45 skipping to change at page 32, line 45
| (Create a port mapping | | (Create a port mapping |
| for the user, and | | for the user, and |
| associate it with the | | associate it with the |
| internal IP address | | internal IP address |
| and external IP address) | | and external IP address) |
| | | | | |
| | | | | |
| |------Accounting-Request------>| | |------Accounting-Request------>|
| | (IP-Port-Forwarding-Map) | | | (IP-Port-Forwarding-Map) |
Figure 18: RADIUS Message Flow for configuring a forwarding port Figure 18: RADIUS Message Flow for Configuring
mapping a Port Forwarding Mapping
A port forwarding mapping that is created on a CGN device using A port forwarding mapping that is created on a CGN device using the
RADIUS extension as described above may also be changed using RADIUS RADIUS extension as described above may also be changed using a
CoA message [RFC5176] that carries the same RADIUS association. The RADIUS CoA message [RFC5176] that carries the same RADIUS
CoA message may be sent from the RADIUS server directly to the NAS, association. The CoA message may be sent from the RADIUS server
which once accepts and sends back a RADIUS CoA ACK message, the new directly to the NAS, and once the RADIUS CoA ACK message is accepted
port forwarding mapping then replaces the previous one. and sent back, the new port forwarding mapping then replaces the
previous one.
Figure 19 illustrates how RADIUS protocol is used to change an Figure 19 illustrates how the RADIUS protocol is used to change an
existing port mapping from (a:X) to (a:Y), where "a" is an internal 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 port, and "X" and "Y" are external ports, respectively, for a
specific user with a specific IP address specific user with a specific IP address
Host CGN/NAS AAA Host CGN/NAS AAA
| BNG Server | BNG Server
| | | | | |
| Internal IP Address | | Internal IP Address |
| Port Map (a:X) | | Port Map (a:X) |
| | | | | |
| |<---------CoA Request----------| | |<---------CoA Request----------|
| | (IP-Port-Forwarding-Map) | | | (IP-Port-Forwarding-Map) |
| | | | | |
| Internal IP Address | | Internal IP Address |
| Port Map (a:Y) | | Port Map (a:Y) |
| | | | | |
| |---------CoA Response--------->| | |---------CoA Response--------->|
| | (IP-Port-Forwarding-Map) | | | (IP-Port-Forwarding-Map) |
Figure 19: RADIUS Message Flow for changing a user's forwarding port Figure 19: RADIUS Message Flow for Changing
mapping a User's Port Forwarding Mapping
4.1.4. An Example 4.1.4. An Example
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
on a CGN device for Joe, and is configured on a RADIUS server. Also, ports on a CGN device for Joe and it is configured on a RADIUS
Joe asks for a pre-defined port forwarding mapping on the CGN device server. Also, Joe asks for a pre-defined port forwarding mapping on
for his web cam applications (external port 5000 maps to internal the CGN device for his web cam applications (external port 5000 maps
port 1234). to internal port 1234).
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 (500) and the forwarding port server conveys the TCP/UDP port limit (500) and the port forwarding
mapping (external port 5000 to internal port 1234) to the CGN device, mapping (external port 5000 to internal port 1234) to the CGN device
using IP-Port-Limit-Info Attribute and IP-Port-Forwarding-Map using the IP-Port-Limit-Info Attribute and IP-Port-Forwarding-Map
attribute, respectively, carried by an Access-Accept message to the Attribute, respectively, carried by an Access-Accept message to the
BNG where NAS and CGN co-located. BNG where NAS and CGN are 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 CGN device decides to allocate a small port pool that contains 40 the CGN device decides to allocate a small port pool that contains 40
consecutive ports, from 3500 to 3540, inclusively, and also assign a consecutive ports, from 3500 to 3540, inclusively, and also assigns a
shared IPv4 address 192.0.2.15, for Joe. The CGN device also randomly shared IPv4 address 192.0.2.15 for Joe. The CGN device also randomly
selects one port from the allocated range (say 3519) and use that selects one port from the allocated range (say, 3519) and uses that
port to replace the original source port in outbound IP packets. port to replace the original source port in outbound IP packets.
For accounting purpose, the CGN device passes this port range For accounting purposes, the CGN 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
RADIUS server using IP-Port-Range attribute carried by an Accounting- RADIUS server using IP-Port-Range Attribute carried by an
Request message. Accounting-Request message.
When Joe works on more applications with more outbound IP mappings When Joe works on more applications with more outbound IP mappings
and the port pool (3500-3540) is close to exhaust, the CGN device and the port pool (3500-3540) is close to exhaust, the CGN device
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-Info Attribute with 1000 ports to the that carries the IP-Port-Limit-Info Attribute with 1000 ports to the
CGN device; the CGN device in turn sends back a CoA-ACK message. CGN device; the CGN device in turn sends back a CoA-ACK message.
With that, Joe enjoys more available TCP/UDP ports for his With that, Joe enjoys more available TCP/UDP ports for his
applications. applications.
When Joe is not using his service, most of the IP mappings are closed When Joe is not using his service, most of the IP mappings are closed
with their associated TCP/UDP ports released on the CGN device, which with their associated TCP/UDP ports released on the CGN device, which
then sends the relevant information back to the RADIUS server using then sends the relevant information back to the RADIUS server using
IP-Port-Range attribute carried by Accounting-Request message. the IP-Port-Range Attribute carried by the Accounting-Request
message.
Throughout Joe's connection with his ISP Internet service, Throughout Joe's connection with his ISP, applications can
applications can communicate with his web cam at home from external communicate with his web cam at home from the external realm, thus
realm directly traversing the pre-configured mapping on the CGN 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
deallocate 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 that occurs
when a visiting User Equipment (UE) connects to a CPE offering WLAN when the visiting User Equipment (UE) connects to a CPE offering WLAN
service. 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.
UE CPE CGN AAA UE CPE CGN AAA
| BNG Server | BNG Server
| | | | | |
| | | | | |
|----Service Request------>| | |----Service Request------>| |
skipping to change at page 32, line 36 skipping to change at page 35, line 45
| | | | | | | |
| | | | | | | |
| (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 deallocation) | | | for deallocation) |
| | | | | |
Figure 20: RADIUS Message Flow for reporting CPE allocation/ Figure 20: RADIUS Message Flow for Reporting CPE
deallocation of a port set to a visiting UE Allocation/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-Info: 241.5. o IP-Port-Limit-Info: 241.5
o IP-Port-Range: 241.6. o IP-Port-Range: 241.6
o IP-Port-Forwarding-Map: 241.7. o IP-Port-Forwarding-Map: 241.7
The following table provides a guide as what type of RADIUS packets The following table provides a guide as to what type of RADIUS
that may contain these attributes, and in what quantity. packets 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+ 241.5 IP-Port-Limit-Info 0+ 0+ 0 0 0+ 241.5 IP-Port-Limit-Info
0 0 0 0 0+ 241.6 IP-Port-Range 0 0 0 0 0+ 241.6 IP-Port-Range
0+ 0+ 0 0 0+ 241.7 IP-Port-Forwarding-Map 0+ 0+ 0 0 0+ 241.7 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] and [RFC5176] for CoA ones already identified in RADIUS documents [RFC2865] and [RFC5176]
messages. Known RADIUS vulnerabilities apply to this specification. for CoA messages. Known RADIUS vulnerabilities apply to this
For example, if RADIUS packets are sent in the clear, an attacker in specification. For example, if RADIUS packets are sent in the clear,
the communication path between the RADIUS client and server may glean an attacker in the communication path between the RADIUS client and
information that it will use to prevent a legitimate user to access server may glean information that it will use to prevent a legitimate
the service by appropriately setting the maximum number of IP ports user from accessing the service by appropriately setting the maximum
conveyed in an IP-Port-Limit-Info Attribute, exhaust the port quota number of IP ports conveyed in an IP-Port-Limit-Info Attribute;
of a user by installing many mapping entries (IP-Port-Forwarding-Map exhaust the port quota of a user by installing many mapping entries
Attribute), prevent incoming traffic to be delivered to its (IP-Port-Forwarding-Map Attribute); prevent incoming traffic from
legitimate destination by manipulating the mapping entries installed being delivered to its legitimate destination by manipulating the
by means of an IP-Port-Forwarding-Map Attribute, discover the IP mapping entries installed by means of an IP-Port-Forwarding-Map
address and port range assigned to a given user and which is reported Attribute; discover the IP address and port range that are assigned
in an IP-Port-Range Attribute, etc. The root cause of these attack to a given user and reported in an IP-Port-Range Attribute; and so
vectors is the communication between the RADIUS client and server. on. The root cause of these attack vectors is the communication
between the RADIUS client and server.
The IP-Port-Local-Id TLV includes an identifier of which the type and The IP-Port-Local-Id TLV includes an identifier of which the type and
length is deployment and implementation dependent. This identifier length is deployment and implementation dependent. This identifier
might carry privacy sensitive information. It is therefore might carry privacy-sensitive information. It is therefore
RECOMMENDED to utilize identifiers that do not have such privacy RECOMMENDED to utilize identifiers that do not have such privacy
concerns. concerns.
If there is any error in a Radius Accounting-Request packet sent from If there is any error in a RADIUS Accounting-Request packet sent
a RADIUS client to the server, the RADIUS server MUST NOT send from a RADIUS client to the server, the RADIUS server MUST NOT send
response to the client (refer to [RFC2866]). Examples of the errors a response to the client (refer to [RFC2866]). Examples of the
include the erroneous port range in IP-Port-Range Attribute, errors include the erroneous port range in the
inconsistent port mapping in IP-Port-Forwarding-Map Attribute, etc. IP-Port-Range Attribute, inconsistent port mapping in the
IP-Port-Forwarding-Map Attribute, etc.
This document targets deployments where a trusted relationship is in This document targets deployments where a trusted relationship is in
place between the RADIUS client and server with communication place between the RADIUS client and server with communication
optionally secured by IPsec or Transport Layer Security (TLS) optionally secured by IPsec or Transport Layer Security (TLS)
[RFC6614]. [RFC6614].
7. IANA Considerations 7. IANA Considerations
This document requires new code point assignments for both IPFIX Per this document, IANA has made new code point assignments for both
Information Elements and RADIUS attributes as explained in the IPFIX Information Elements and RADIUS attributes as explained in the
following sub-sections. following subsections.
7.1. IANA Considerations on New IPFIX Information Elements 7.1. New IPFIX Information Elements
The following is a new IPFIX Information Element as requested by this The following IPFIX Information Element has been registered (refer to
document (refer to Section 3.2.2) : Section 3.2.2):
o sourceTransportPortsLimit: o sourceTransportPortsLimit:
* Name: sourceTransportPortsLimit. * Name: sourceTransportPortsLimit
* Element ID: 458. * Element ID: 458
* Description: This Information Element contains the maximum * Description: This Information Element contains the maximum
number of IP source transport ports that can be used by an end number of IP source transport ports that can be used by an end
user when sending IP packets; each user is associated with one user when sending IP packets; each user is associated with one
or more (source) IPv4 or IPv6 addresses. This IE is or more (source) IPv4 or IPv6 addresses. This Information
particularly useful in address sharing deployments that adhere Element is particularly useful in address-sharing deployments
to REQ-4 of [RFC6888]. Limiting the number of ports assigned that adhere to REQ-4 of [RFC6888]. Limiting the number of
to each user ensures fairness among users and mitigates the ports assigned to each user ensures fairness among users and
denial-of-service attack that a user could launch against other mitigates the denial-of-service attack that a user could launch
users through the address sharing device in order to grab more against other users through the address-sharing device in order
ports. to grab more ports.
* Data type: unsigned16.
* Data type semantics: totalCounter. * Data type: unsigned16
* Data type semantics: totalCounter
* Data type unit: ports. * Data type unit: ports
* Data value range: from 1 to 65535. * Data value range: from 1 to 65535
7.2. IANA Considerations on New RADIUS Attributes 7.2. New RADIUS Attributes
The authors request that Attribute Types and Attribute Values defined The Attribute Types defined in this document have been registered by
in this document be registered by the Internet Assigned Numbers IANA from the RADIUS namespace 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 has placed 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, as
entitled "IP-Port-Limit-Info" (see Section 3.1.1), "IP-Port-Range" follows, from the Short Extended Space of [RFC6929]:
(see Section 3.1.2) and "IP-Port-Forwarding-Map" (see Section 3.1.3),
with assigned values of 241.5, 241.6 and 241.7 from the Short
Extended Space of [RFC6929]:
Type Name Meaning Type Description Data Type Reference
---- ---- ------- ---- ----------- --------- ---------
241.5 IP-Port-Limit-Info see Section 3.1.1 241.5 IP-Port-Limit-Info tlv Section 3.1.1
241.6 IP-Port-Range see Section 3.1.2 241.6 IP-Port-Range tlv Section 3.1.2
241.7 IP-Port-Forwarding-Map see Section 3.1.3 241.7 IP-Port-Forwarding-Map tlv Section 3.1.3
7.3. IANA Considerations on New RADIUS TLVs 7.3. New RADIUS TLVs
IANA has created a new registry called "RADIUS IP Port Configuraion IANA has created a new registry called "RADIUS IP Port Configuration
and Reporting TLVs". All TLVs in this registry have one or more and Reporting TLVs". All TLVs in this registry have one or more
parent Radius attributes in nesting (refer to [RFC6929]. This parent RADIUS attributes in nesting (refer to [RFC6929]). This
registray contains the following TLVs: registry contains the following TLVs:
Value Name Definition Value Description Data Type Reference
----- ----- ---------- ----- ----------- --------- ---------
0 Reserved 0 Reserved
1 IP-Port-Type see Section 3.2.1 1 IP-Port-Type integer Section 3.2.1
2 IP-Port-Limit see Section 3.2.2 2 IP-Port-Limit integer Section 3.2.2
3 IP-Port-Ext-IPv4-Addr see Section 3.2.3 3 IP-Port-Ext-IPv4-Addr ipv4addr Section 3.2.3
4 IP-Port-Int-IPv4-Addr see Section 3.2.4 4 IP-Port-Int-IPv4-Addr ipv4addr Section 3.2.4
5 IP-Port-Int-IPv6-Addr see Section 3.2.5 5 IP-Port-Int-IPv6-Addr ipv4addr Section 3.2.5
6 IP-Port-Int-Port see Section 3.2.6 6 IP-Port-Int-Port integer Section 3.2.6
7 IP-Port-Ext-Port see Section 3.2.7 7 IP-Port-Ext-Port integer Section 3.2.7
8 IP-Port-Alloc see Section 3.2.8 8 IP-Port-Alloc integer Section 3.2.8
9 IP-Port-Range-Start see Section 3.2.9 9 IP-Port-Range-Start integer Section 3.2.9
10 IP-Port-Range-End see Section 3.2.10 10 IP-Port-Range-End integer Section 3.2.10
11 IP-Port-Local-Id see Section 3.2.11 11 IP-Port-Local-Id string Section 3.2.11
12-255 Unsigned 12-255 Unassigned
The registration procedure for this registry is Standards Action as The registration procedure for this registry is Standards Action as
defined in [RFC5226]. defined in [RFC5226].
8. Acknowledgements 8. References
Many thanks to Dan Wing, Roberta Maglione, Daniel Derksen, David
Thaler, Alan Dekok, Lionel Morand, and Peter Deacon for their useful
comments and suggestions.
Special thanks to Lionel Morand for the Shepherd review and to
Kathleen Moriarty for the AD review.
Thanks to Carl Wallace, Tim Chown, and Ben Campbell for the detailed
review.
9. References
9.1. Normative References
[I-D.ietf-radext-datatypes] 8.1. Normative References
DeKok, A., "Data Types in the Remote Authentication Dial-
In User Service Protocol (RADIUS)", draft-ietf-radext-
datatypes-08 (work in progress), October 2016.
[IPFIX] IANA, "IP Flow Information Export (IPFIX) Entities", [IPFIX] IANA, "IP Flow Information Export (IPFIX) Entities",
<http://www.iana.org/assignments/ipfix/ipfix.xhtml>. <http://www.iana.org/assignments/ipfix/>.
[ProtocolNumbers] [ProtocolNumbers]
IANA, "Protocol Numbers", IANA, "Protocol Numbers",
<http://www.iana.org/assignments/protocol-numbers/ <http://www.iana.org/assignments/protocol-numbers/>.
protocol-numbers.xhtml>.
[RFC2119] Bradner, S., "Key words for use in RFCs to Indicate [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate
Requirement Levels", BCP 14, RFC 2119, Requirement Levels", BCP 14, RFC 2119,
DOI 10.17487/RFC2119, March 1997, DOI 10.17487/RFC2119, March 1997,
<http://www.rfc-editor.org/info/rfc2119>. <http://www.rfc-editor.org/info/rfc2119>.
[RFC2865] Rigney, C., Willens, S., Rubens, A., and W. Simpson, [RFC2865] Rigney, C., Willens, S., Rubens, A., and W. Simpson,
"Remote Authentication Dial In User Service (RADIUS)", "Remote Authentication Dial In User Service (RADIUS)",
RFC 2865, DOI 10.17487/RFC2865, June 2000, RFC 2865, DOI 10.17487/RFC2865, June 2000,
<http://www.rfc-editor.org/info/rfc2865>. <http://www.rfc-editor.org/info/rfc2865>.
skipping to change at page 36, line 47 skipping to change at page 39, line 44
[RFC5226] Narten, T. and H. Alvestrand, "Guidelines for Writing an [RFC5226] Narten, T. and H. Alvestrand, "Guidelines for Writing an
IANA Considerations Section in RFCs", BCP 26, RFC 5226, IANA Considerations Section in RFCs", BCP 26, RFC 5226,
DOI 10.17487/RFC5226, May 2008, DOI 10.17487/RFC5226, May 2008,
<http://www.rfc-editor.org/info/rfc5226>. <http://www.rfc-editor.org/info/rfc5226>.
[RFC6929] DeKok, A. and A. Lior, "Remote Authentication Dial In User [RFC6929] DeKok, A. and A. Lior, "Remote Authentication Dial In User
Service (RADIUS) Protocol Extensions", RFC 6929, Service (RADIUS) Protocol Extensions", RFC 6929,
DOI 10.17487/RFC6929, April 2013, DOI 10.17487/RFC6929, April 2013,
<http://www.rfc-editor.org/info/rfc6929>. <http://www.rfc-editor.org/info/rfc6929>.
[RFC7012] Claise, B., Ed. and B. Trammell, Ed., "Information Model [RFC7012] Claise, B., Ed., and B. Trammell, Ed., "Information Model
for IP Flow Information Export (IPFIX)", RFC 7012, for IP Flow Information Export (IPFIX)", RFC 7012,
DOI 10.17487/RFC7012, September 2013, DOI 10.17487/RFC7012, September 2013,
<http://www.rfc-editor.org/info/rfc7012>. <http://www.rfc-editor.org/info/rfc7012>.
9.2. Informative References [RFC8044] DeKok, A., "Data Types in RADIUS", RFC 8044,
DOI 10.17487/RFC8044, January 2017,
<http://www.rfc-editor.org/info/rfc8044>.
[I-D.gundavelli-v6ops-community-wifi-svcs] 8.2. Informative References
Gundavelli, S., Grayson, M., Seite, P., and Y. Lee,
"Service Provider Wi-Fi Services Over Residential
Architectures", draft-gundavelli-v6ops-community-wifi-
svcs-06 (work in progress), April 2013.
[RFC0768] Postel, J., "User Datagram Protocol", STD 6, RFC 768, [RFC768] Postel, J., "User Datagram Protocol", STD 6, RFC 768,
DOI 10.17487/RFC0768, August 1980, DOI 10.17487/RFC0768, August 1980,
<http://www.rfc-editor.org/info/rfc768>. <http://www.rfc-editor.org/info/rfc768>.
[RFC0793] Postel, J., "Transmission Control Protocol", STD 7, [RFC793] Postel, J., "Transmission Control Protocol", STD 7,
RFC 793, DOI 10.17487/RFC0793, September 1981, RFC 793, DOI 10.17487/RFC0793, September 1981,
<http://www.rfc-editor.org/info/rfc793>. <http://www.rfc-editor.org/info/rfc793>.
[RFC1918] Rekhter, Y., Moskowitz, B., Karrenberg, D., de Groot, G., [RFC1918] Rekhter, Y., Moskowitz, B., Karrenberg, D., de Groot, G.,
and E. Lear, "Address Allocation for Private Internets", and E. Lear, "Address Allocation for Private Internets",
BCP 5, RFC 1918, DOI 10.17487/RFC1918, February 1996, BCP 5, RFC 1918, DOI 10.17487/RFC1918, February 1996,
<http://www.rfc-editor.org/info/rfc1918>. <http://www.rfc-editor.org/info/rfc1918>.
[RFC2866] Rigney, C., "RADIUS Accounting", RFC 2866, [RFC2866] Rigney, C., "RADIUS Accounting", RFC 2866,
DOI 10.17487/RFC2866, June 2000, DOI 10.17487/RFC2866, June 2000,
skipping to change at page 38, line 10 skipping to change at page 40, line 49
Aboba, "Dynamic Authorization Extensions to Remote Aboba, "Dynamic Authorization Extensions to Remote
Authentication Dial In User Service (RADIUS)", RFC 5176, Authentication Dial In User Service (RADIUS)", RFC 5176,
DOI 10.17487/RFC5176, January 2008, DOI 10.17487/RFC5176, January 2008,
<http://www.rfc-editor.org/info/rfc5176>. <http://www.rfc-editor.org/info/rfc5176>.
[RFC6146] Bagnulo, M., Matthews, P., and I. van Beijnum, "Stateful [RFC6146] Bagnulo, M., Matthews, P., and I. van Beijnum, "Stateful
NAT64: Network Address and Protocol Translation from IPv6 NAT64: Network Address and Protocol Translation from IPv6
Clients to IPv4 Servers", RFC 6146, DOI 10.17487/RFC6146, Clients to IPv4 Servers", RFC 6146, DOI 10.17487/RFC6146,
April 2011, <http://www.rfc-editor.org/info/rfc6146>. April 2011, <http://www.rfc-editor.org/info/rfc6146>.
[RFC6158] DeKok, A., Ed. and G. Weber, "RADIUS Design Guidelines", [RFC6158] DeKok, A., Ed., and G. Weber, "RADIUS Design Guidelines",
BCP 158, RFC 6158, DOI 10.17487/RFC6158, March 2011, BCP 158, RFC 6158, DOI 10.17487/RFC6158, March 2011,
<http://www.rfc-editor.org/info/rfc6158>. <http://www.rfc-editor.org/info/rfc6158>.
[RFC6269] Ford, M., Ed., Boucadair, M., Durand, A., Levis, P., and [RFC6269] Ford, M., Ed., Boucadair, M., Durand, A., Levis, P., and
P. Roberts, "Issues with IP Address Sharing", RFC 6269, P. Roberts, "Issues with IP Address Sharing", RFC 6269,
DOI 10.17487/RFC6269, June 2011, DOI 10.17487/RFC6269, June 2011,
<http://www.rfc-editor.org/info/rfc6269>. <http://www.rfc-editor.org/info/rfc6269>.
[RFC6333] Durand, A., Droms, R., Woodyatt, J., and Y. Lee, "Dual- [RFC6333] Durand, A., Droms, R., Woodyatt, J., and Y. Lee,
Stack Lite Broadband Deployments Following IPv4 "Dual-Stack Lite Broadband Deployments Following IPv4
Exhaustion", RFC 6333, DOI 10.17487/RFC6333, August 2011, Exhaustion", RFC 6333, DOI 10.17487/RFC6333, August 2011,
<http://www.rfc-editor.org/info/rfc6333>. <http://www.rfc-editor.org/info/rfc6333>.
[RFC6598] Weil, J., Kuarsingh, V., Donley, C., Liljenstolpe, C., and [RFC6598] Weil, J., Kuarsingh, V., Donley, C., Liljenstolpe, C., and
M. Azinger, "IANA-Reserved IPv4 Prefix for Shared Address M. Azinger, "IANA-Reserved IPv4 Prefix for Shared Address
Space", BCP 153, RFC 6598, DOI 10.17487/RFC6598, April Space", BCP 153, RFC 6598, DOI 10.17487/RFC6598,
2012, <http://www.rfc-editor.org/info/rfc6598>. April 2012, <http://www.rfc-editor.org/info/rfc6598>.
[RFC6614] Winter, S., McCauley, M., Venaas, S., and K. Wierenga, [RFC6614] Winter, S., McCauley, M., Venaas, S., and K. Wierenga,
"Transport Layer Security (TLS) Encryption for RADIUS", "Transport Layer Security (TLS) Encryption for RADIUS",
RFC 6614, DOI 10.17487/RFC6614, May 2012, RFC 6614, DOI 10.17487/RFC6614, May 2012,
<http://www.rfc-editor.org/info/rfc6614>. <http://www.rfc-editor.org/info/rfc6614>.
[RFC6887] Wing, D., Ed., Cheshire, S., Boucadair, M., Penno, R., and [RFC6887] Wing, D., Ed., Cheshire, S., Boucadair, M., Penno, R., and
P. Selkirk, "Port Control Protocol (PCP)", RFC 6887, P. Selkirk, "Port Control Protocol (PCP)", RFC 6887,
DOI 10.17487/RFC6887, April 2013, DOI 10.17487/RFC6887, April 2013,
<http://www.rfc-editor.org/info/rfc6887>. <http://www.rfc-editor.org/info/rfc6887>.
skipping to change at page 39, line 10 skipping to change at page 42, line 5
"Analysis of Potential Solutions for Revealing a Host "Analysis of Potential Solutions for Revealing a Host
Identifier (HOST_ID) in Shared Address Deployments", Identifier (HOST_ID) in Shared Address Deployments",
RFC 6967, DOI 10.17487/RFC6967, June 2013, RFC 6967, DOI 10.17487/RFC6967, June 2013,
<http://www.rfc-editor.org/info/rfc6967>. <http://www.rfc-editor.org/info/rfc6967>.
[RFC7785] Vinapamula, S. and M. Boucadair, "Recommendations for [RFC7785] Vinapamula, S. and M. Boucadair, "Recommendations for
Prefix Binding in the Context of Softwire Dual-Stack Prefix Binding in the Context of Softwire Dual-Stack
Lite", RFC 7785, DOI 10.17487/RFC7785, February 2016, Lite", RFC 7785, DOI 10.17487/RFC7785, February 2016,
<http://www.rfc-editor.org/info/rfc7785>. <http://www.rfc-editor.org/info/rfc7785>.
[TR-146] Broadband Forum, "TR-146: Subscriber Sessions", [TR-146] Broadband Forum, "TR-146: Subscriber Sessions", Broadband
<http://www.broadband-forum.org/technical/download/ Forum Technical Report 146, Issue 1, May 2013,
TR-146.pdf>. <http://www.broadband-forum.org/technical/
download/TR-146.pdf>.
[WIFI-SERVICES]
Gundavelli, S., Grayson, M., Seite, P., and Y. Lee,
"Service Provider Wi-Fi Services Over Residential
Architectures", Work in Progress,
draft-gundavelli-v6ops-community-wifi-svcs-06, April 2013.
Acknowledgments
Many thanks to Dan Wing, Roberta Maglione, Daniel Derksen, David
Thaler, Alan DeKok, Lionel Morand, and Peter Deacon for their useful
comments and suggestions.
Special thanks to Lionel Morand for the Shepherd review and to
Kathleen Moriarty for the AD review.
Thanks to Carl Wallace, Tim Chown, and Ben Campbell for the detailed
review.
Authors' Addresses Authors' Addresses
Dean Cheng Dean Cheng
Huawei Huawei
2330 Central Expressway 2330 Central Expressway
Santa Clara, California 95050 Santa Clara, California 95050
USA United States of America
Email: dean.cheng@huawei.com Email: dean.cheng@huawei.com
Jouni Korhonen Jouni Korhonen
Broadcom Corporation Broadcom Corporation
3151 Zanker Road 3151 Zanker Road
San Jose 95134 San Jose, California 95134
USA United States of America
Email: jouni.nospam@gmail.com Email: jouni.nospam@gmail.com
Mohamed Boucadair Mohamed Boucadair
Orange Orange
Rennes Rennes
France France
Email: mohamed.boucadair@orange.com Email: mohamed.boucadair@orange.com
Senthil Sivakumar Senthil Sivakumar
Cisco Systems Cisco Systems
7100-8 Kit Creek Road 7100-8 Kit Creek Road
Research Triangle Park, North Carolina Research Triangle Park, North Carolina
USA United States of America
Email: ssenthil@cisco.com Email: ssenthil@cisco.com
 End of changes. 218 change blocks. 
555 lines changed or deleted 553 lines changed or added

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