< draft-ietf-radext-ip-port-radius-ext-16.txt | draft-ietf-radext-ip-port-radius-ext-17.txt > | |||
---|---|---|---|---|
skipping to change at page 1, line 14 ¶ | skipping to change at page 1, line 14 ¶ | |||
Internet-Draft Huawei | Internet-Draft Huawei | |||
Intended status: Standards Track J. Korhonen | Intended status: Standards Track J. Korhonen | |||
Expires: May 18, 2017 Broadcom Corporation | Expires: May 18, 2017 Broadcom Corporation | |||
M. Boucadair | M. Boucadair | |||
Orange | Orange | |||
S. Sivakumar | S. Sivakumar | |||
Cisco Systems | Cisco Systems | |||
November 14, 2016 | November 14, 2016 | |||
RADIUS Extensions for IP Port Configuration and Reporting | RADIUS Extensions for IP Port Configuration and Reporting | |||
draft-ietf-radext-ip-port-radius-ext-16 | 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 can be used in various deployment scenarios such as | mechanism can be used in various deployment scenarios such as | |||
Carrier-Grade NAT, IPv4/IPv6 translators, Provider WLAN Gateway, etc. | Carrier-Grade NAT, IPv4/IPv6 translators, Provider WLAN Gateway, etc. | |||
This document defines a mapping between some RADIUS attributes and | This document defines a mapping between some RADIUS attributes and | |||
skipping to change at page 3, line 8 ¶ | skipping to change at page 3, line 8 ¶ | |||
4.2. Report Assigned Port Set for a Visiting UE . . . . . . . 31 | 4.2. Report Assigned Port Set for a Visiting UE . . . . . . . 31 | |||
5. Table of Attributes . . . . . . . . . . . . . . . . . . . . . 32 | 5. Table of Attributes . . . . . . . . . . . . . . . . . . . . . 32 | |||
6. Security Considerations . . . . . . . . . . . . . . . . . . . 33 | 6. Security Considerations . . . . . . . . . . . . . . . . . . . 33 | |||
7. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 34 | 7. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 34 | |||
7.1. IANA Considerations on New IPFIX Information | 7.1. IANA Considerations on New IPFIX Information | |||
Elements . . . . . . . . . . . . . . . . . . . . . . . . 34 | Elements . . . . . . . . . . . . . . . . . . . . . . . . 34 | |||
7.2. IANA Considerations on New RADIUS Attributes . . . . . . 34 | 7.2. IANA Considerations on New RADIUS Attributes . . . . . . 34 | |||
7.3. IANA Considerations on New RADIUS TLVs . . . . . . . . . 35 | 7.3. IANA Considerations on New RADIUS TLVs . . . . . . . . . 35 | |||
8. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 35 | 8. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 35 | |||
9. References . . . . . . . . . . . . . . . . . . . . . . . . . 35 | 9. References . . . . . . . . . . . . . . . . . . . . . . . . . 36 | |||
9.1. Normative References . . . . . . . . . . . . . . . . . . 36 | 9.1. Normative References . . . . . . . . . . . . . . . . . . 36 | |||
9.2. Informative References . . . . . . . . . . . . . . . . . 37 | 9.2. Informative References . . . . . . . . . . . . . . . . . 37 | |||
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 39 | 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 | |||
skipping to change at page 35, line 19 ¶ | skipping to change at page 35, line 19 ¶ | |||
Short Extended Space of [RFC6929]: | Short Extended Space of [RFC6929]: | |||
Type Name Meaning | Type Name Meaning | |||
---- ---- ------- | ---- ---- ------- | |||
241.TBD1 IP-Port-Limit-Info see Section 3.1.1 | 241.TBD1 IP-Port-Limit-Info see Section 3.1.1 | |||
241.TBD2 IP-Port-Range see Section 3.1.2 | 241.TBD2 IP-Port-Range see Section 3.1.2 | |||
241.TBD3 IP-Port-Forwarding-Map see Section 3.1.3 | 241.TBD3 IP-Port-Forwarding-Map see Section 3.1.3 | |||
7.3. IANA Considerations on New RADIUS TLVs | 7.3. IANA Considerations on New RADIUS TLVs | |||
This specification requests allocation of the following TLVs: | IANA has created a new registry called "RADIUS IP Port Configuraion | |||
and Reporting TLVs". All TLVs in this registry have one or more | ||||
parent Radius attributes in nesting (refer to [RFC6929]. This | ||||
registray contains the following TLVs: | ||||
Name Value Meaning | Value Name Definition | |||
---- ----- ------- | ----- ----- ---------- | |||
IP-Port-Type 1 see Section 3.2.1 | 0 Reserved | |||
IP-Port-Limit 2 see Section 3.2.2 | 1 IP-Port-Type see Section 3.2.1 | |||
IP-Port-Ext-IPv4-Addr 3 see Section 3.2.3 | 2 IP-Port-Limit see Section 3.2.2 | |||
IP-Port-Int-IPv4-Addr 4 see Section 3.2.4 | 3 IP-Port-Ext-IPv4-Addr see Section 3.2.3 | |||
IP-Port-Int-IPv6-Addr 5 see Section 3.2.5 | 4 IP-Port-Int-IPv4-Addr see Section 3.2.4 | |||
IP-Port-Int-Port 6 see Section 3.2.6 | 5 IP-Port-Int-IPv6-Addr see Section 3.2.5 | |||
IP-Port-Ext-Port 7 see Section 3.2.7 | 6 IP-Port-Int-Port see Section 3.2.6 | |||
IP-Port-Alloc 8 see Section 3.2.8 | 7 IP-Port-Ext-Port see Section 3.2.7 | |||
IP-Port-Range-Start 9 see Section 3.2.9 | 8 IP-Port-Alloc see Section 3.2.8 | |||
IP-Port-Range-End 10 see Section 3.2.10 | 9 IP-Port-Range-Start see Section 3.2.9 | |||
IP-Port-Local-Id 11 see Section 3.2.11 | 10 IP-Port-Range-End see Section 3.2.10 | |||
11 IP-Port-Local-Id see Section 3.2.11 | ||||
12-255 Unsigned | ||||
The registration procedure for this registry is Standards Action as | ||||
defined in [RFC5226]. | ||||
8. Acknowledgements | 8. Acknowledgements | |||
Many thanks to Dan Wing, Roberta Maglione, Daniel Derksen, David | Many thanks to Dan Wing, Roberta Maglione, Daniel Derksen, David | |||
Thaler, Alan Dekok, Lionel Morand, and Peter Deacon for their useful | Thaler, Alan Dekok, Lionel Morand, and Peter Deacon for their useful | |||
comments and suggestions. | comments and suggestions. | |||
Special thanks to Lionel Morand for the Shepherd review and to | Special thanks to Lionel Morand for the Shepherd review and to | |||
Kathleen Moriarty for the AD review. | Kathleen Moriarty for the AD review. | |||
End of changes. 4 change blocks. | ||||
16 lines changed or deleted | 24 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/ |