--- 1/draft-ietf-radext-ip-port-radius-ext-16.txt 2016-11-14 20:13:08.045052799 -0800 +++ 2/draft-ietf-radext-ip-port-radius-ext-17.txt 2016-11-14 20:13:08.121054670 -0800 @@ -1,23 +1,23 @@ Network Working Group D. Cheng Internet-Draft Huawei Intended status: Standards Track J. Korhonen -Expires: May 7, 2017 Broadcom Corporation +Expires: May 18, 2017 Broadcom Corporation M. Boucadair Orange S. Sivakumar Cisco Systems - November 3, 2016 + November 14, 2016 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 This document defines three new RADIUS attributes. For devices that implement IP port ranges, these attributes are used to communicate with a RADIUS server in order to configure and report IP transport ports, as well as mapping behavior for specific hosts. This mechanism can be used in various deployment scenarios such as Carrier-Grade NAT, IPv4/IPv6 translators, Provider WLAN Gateway, etc. This document defines a mapping between some RADIUS attributes and @@ -37,21 +37,21 @@ Internet-Drafts are working documents of the Internet Engineering Task Force (IETF). Note that other groups may also distribute working documents as Internet-Drafts. The list of current Internet- Drafts is at http://datatracker.ietf.org/drafts/current/. Internet-Drafts are draft documents valid for a maximum of six months and may be updated, replaced, or obsoleted by other documents at any time. It is inappropriate to use Internet-Drafts as reference material or to cite them other than as "work in progress." - This Internet-Draft will expire on May 7, 2017. + This Internet-Draft will expire on May 18, 2017. Copyright Notice Copyright (c) 2016 IETF Trust and the persons identified as the document authors. All rights reserved. This document is subject to BCP 78 and the IETF Trust's Legal Provisions Relating to IETF Documents (http://trustee.ietf.org/license-info) in effect on the date of publication of this document. Please review these documents @@ -91,21 +91,21 @@ 4.2. Report Assigned Port Set for a Visiting UE . . . . . . . 31 5. Table of Attributes . . . . . . . . . . . . . . . . . . . . . 32 6. Security Considerations . . . . . . . . . . . . . . . . . . . 33 7. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 34 7.1. IANA Considerations on New IPFIX Information Elements . . . . . . . . . . . . . . . . . . . . . . . . 34 7.2. IANA Considerations on New RADIUS Attributes . . . . . . 34 7.3. IANA Considerations on New RADIUS TLVs . . . . . . . . . 35 8. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 35 - 9. References . . . . . . . . . . . . . . . . . . . . . . . . . 35 + 9. References . . . . . . . . . . . . . . . . . . . . . . . . . 36 9.1. Normative References . . . . . . . . . . . . . . . . . . 36 9.2. Informative References . . . . . . . . . . . . . . . . . 37 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 39 1. Introduction In a broadband network, customer information is usually stored on a RADIUS server [RFC2865]. At the time when a user initiates an IP connection request, if this request is authorized, the RADIUS server will populate the user's configuration information to the Network @@ -301,31 +301,31 @@ 0 1 2 3 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | Type | Length | Extended-Type | Value ... +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ Figure 1 Type - 241 (To be confirmed by IANA). + 241 Length This field indicates the total length in bytes of all fields of this attribute, including the Type, Length, Extended-Type, and the entire length of the embedded TLVs. Extended-Type - TBD1. + 5 Value This field contains a set of TLVs as follows: IP-Port-Type TLV This TLV contains a value that indicates the IP port type. Refer to Section 3.2.1. @@ -341,21 +341,21 @@ instructed by an AAA server. IP-Port-Ext-IPv4-Addr TLV This TLV contains the IPv4 address that is associated with the IP port limit contained in the IP-Port-Limit TLV. This TLV is optionally included as part of the IP-Port-Limit-Info Attribute. Refer to Section 3.2.3. IP-Port-Limit-Info Attribute is associated with the following - identifier: 241.Extended-Type(TBD1). + identifier: 241.5. 3.1.2. IP-Port-Range Attribute This attribute is of type "TLV" as defined in the RADIUS Protocol Extensions [RFC6929]. It contains some sub-attributes and the requirement is as follows: o The IP-Port-Range Attribute MAY contain the IP-Port-Type TLV (see Section 3.2.1). @@ -407,31 +407,31 @@ 0 1 2 3 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | Type | Length | Extended-Type | Value ... +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ Figure 2 Type - 241 (To be confirmed by IANA). + 241 Length This field indicates the total length in bytes of all fields of this attribute, including the Type, Length, Extended-Type, and the entire length of the embedded TLVs. Extended-Type - TBD2. + 6 Value This field contains a set of TLVs as follows: IP-Port-Type TLV This TLV contains a value that indicates the IP port type. Refer to Section 3.2.1. IP-Port-Alloc TLV @@ -465,21 +465,21 @@ IP-Port-Local-Id TLV This TLV contains a local session identifier at the customer premise, such as MAC address, interface ID, VLAN ID, PPP sessions ID, VRF ID, IP address/prefix, etc. This TLV is optionally included as part of the IP-Port-Range Attribute. Refer to Section 3.2.11. The IP-Port-Range attribute is associated with the following - identifier: 241.Extended-Type(TBD2). + identifier: 241.6. 3.1.3. IP-Port-Forwarding-Map Attribute This attribute is of type "TLV" as defined in the RADIUS Protocol Extensions [RFC6929]. It contains some sub-attributes and the requirement is as follows: o The IP-Port-Forwarding-Map Attribute MAY contain the IP-Port-Type TLV (see Section 3.2.1). @@ -531,31 +531,31 @@ 0 1 2 3 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | Type | Length | Extended-Type | Value .... +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ Figure 3 Type - 241 (To be confirmed by IANA). + 241 Length This field indicates the total length in bytes of all fields of this attribute, including the Type, Length, Extended-Type, and the entire length of the embedded TLVs. Extended-Type - TBD3. + 7 Value This field contains a set of TLVs as follows: IP-Port-Type TLV This TLV contains a value that indicates the IP port type. Refer to Section 3.2.1. @@ -597,21 +597,21 @@ IP-Port-Local-Id TLV This TLV contains a local session identifier at the customer premise, such as MAC address, interface ID, VLAN ID, PPP sessions ID, VRF ID, IP address/prefix, etc. This TLV is optionally included as part of the IP-Port-Forwarding-Map Attribute. Refer to Section 3.2.11. The IP-Port-Forwarding-Map Attribute is associated with the following - identifier: 241.Extended-Type(TBD3). + identifier: 241.7. 3.2. RADIUS TLVs for IP Ports The TLVs that are included in the three attributes (see Section 3.1) are defined in the following sub-sections. These TLVs use the format defined in [RFC6929]. As the three attributes carry similar data, we have defined a common set of TLVs which are used for all three attributes. That is, the TLVs have the same name and number, when 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 @@ -651,38 +651,38 @@ Integer. This field contains the data (unsigned8) of the protocol number defined in [ProtocolNumbers], right justified, and the unused bits in this field MUST be set to zero. Protocols that do not use a port number (e.g., Resource Reservation Protocol (RSVP), IP Encapsulating Security Payload (ESP)) MUST NOT be included in the IP-Port-Type TLV. IP-Port-Type TLV MAY be included in the following Attributes: - o IP-Port-Limit-Info Attribute, identified as 241.TBD1.1 (see + o IP-Port-Limit-Info Attribute, identified as 241.5.1 (see Section 3.1.1). - o IP-Port-Range Attribute, identified as 241.TBD2.1 (see + o IP-Port-Range Attribute, identified as 241.6.1 (see Section 3.1.2). - o IP-Port-Forwarding-Map Attribute, identified as 241.TBD3.1 (see + o IP-Port-Forwarding-Map Attribute, identified as 241.7.1 (see Section 3.1.3). When the IP-Port-Type TLV is included within a RADIUS Attribute, the associated attribute is applied to the IP transport protocol as indicated by the Protocol-Number only, such as TCP, UDP, SCTP, DCCP, etc. 3.2.2. IP-Port-Limit TLV The format of IP-Port-Limit TLV is shown in Figure 5. This attribute - carries IPFIX Information Element "sourceTransportPortsLimit (TBAx1), + carries IPFIX Information Element "sourceTransportPortsLimit (458), 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 IPv6 addresses. 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 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | TLV-Type | Length | sourceTransportPortsLimit +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ sourceTransportPortsLimit | @@ -694,25 +694,25 @@ 2 Length 6 sourceTransportPortsLimit Integer. This field contains the data (unsigned16) of - sourceTransportPortsLimit (TBAx1) defined in IPFIX, right - justified, and the unused bits in this field MUST be set to zero. + sourceTransportPortsLimit (458) defined in IPFIX, right justified, + 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 - Attribute (refer to Section 3.1.1), identified as 241.TBD1.2. + Attribute (refer to Section 3.1.1), identified as 241.5.2. 3.2.3. IP-Port-Ext-IPv4-Addr TLV The format of IP-Port-Ext-IPv4-Addr TLV is shown in Figure 6. This attribute carries IPFIX Information Element 225, "postNATSourceIPv4Address", which is the IPv4 source address after NAT operation (refer to [IPFIX]). 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 @@ -733,28 +733,28 @@ 6 postNATSourceIPv4Address Integer. This field contains the data (ipv4Address) of postNATSourceIPv4Address (225) defined in IPFIX. IP-Port-Ext-IPv4-Addr TLV MAY be included in the following Attributes: - o IP-Port-Limit-Info Attribute, identified as 241.TBD1.3 (see + o IP-Port-Limit-Info Attribute, identified as 241.5.3 (see Section 3.1.1). - o IP-Port-Range Attribute, identified as 241.TBD2.3 (see + o IP-Port-Range Attribute, identified as 241.6.3 (see Section 3.1.2). - o IP-Port-Forwarding-Mapping Attribute, identified as 241.TBD3.3 - (see Section 3.1.3). + o IP-Port-Forwarding-Mapping Attribute, identified as 241.7.3 (see + Section 3.1.3). 3.2.4. IP-Port-Int-IPv4-Addr TLV The format of IP-Port-Int-IPv4 TLV is shown in Figure 7. This attribute carries IPFIX Information Element 8, "sourceIPv4Address", which is the IPv4 source address before NAT operation (refer to [IPFIX]). 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 @@ -774,21 +774,21 @@ 6 sourceIPv4Address Integer. This field contains the data (ipv4Address) of sourceIPv4Address (8) defined in IPFIX. If the internal realm is with IPv4 address family, the IP-Port-Int- IPv4-Addr TLV MUST be included as part of the IP-Port-Forwarding-Map - Attribute (refer to Section 3.1.3), identified as 241.TBD3.4. + Attribute (refer to Section 3.1.3), identified as 241.7.4. 3.2.5. IP-Port-Int-IPv6-Addr TLV The format of IP-Port-Int-IPv6-Addr TLV is shown in Figure 8. This attribute carries IPFIX Information Element 27, "sourceIPv6Address", which is the IPv6 source address before NAT operation (refer to [IPFIX]). 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 @@ -814,21 +814,21 @@ 18 sourceIPv6Address IPv6 address (128 bits). This field contains the data (ipv6Address) of sourceIPv6Address (27) defined in IPFIX. If the internal realm is with IPv6 address family, the IP-Port-Int- IPv6-Addr TLV MUST be included as part of the IP-Port-Forwarding-Map - Attribute (refer to Section 3.1.3), identified as 241.TBD3.5. + Attribute (refer to Section 3.1.3), identified as 241.7.5. 3.2.6. IP-Port-Int-Port TLV The format of IP-Port-Int-Port TLV is shown in Figure 9. This attribute carries IPFIX Information Element 7, "sourceTransportPort", which is the source transport number associated with an internal IPv4 or IPv6 address (refer to [IPFIX]). 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 @@ -849,21 +849,21 @@ 6 sourceTransportPort Integer. This field contains the data (unsigned16) of sourceTrasnportPort (7) defined in IPFIX, right justified, and unused bits MUST be set to zero. IP-Port-Int-Port TLV MUST be included as part of the IP-Port- Forwarding-Map Attribute (refer to Section 3.1.3), identified as - 241.TBD3.6. + 241.7.6. 3.2.7. IP-Port-Ext-Port TLV The format of IP-Port-Ext-Port TLV is shown in Figure 10. This attribute carries IPFIX Information Element 227, "postNAPTSourceTransportPort", which is the transport number associated with an external IPv4 address(refer to [IPFIX]). 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 @@ -883,21 +883,21 @@ 6 postNAPTSourceTransportPort Integer. This field contains the data (unsigned16) of postNAPTSourceTrasnportPort (227) defined in IPFIX, right justified, and unused bits MUST be set to zero. IP-Port-Ext-Port TLV MUST be included as part of the IP-Port- Forwarding-Map Attribute (refer to Section 3.1.3), identified as - 241.TBD3.7. + 241.7.7. 3.2.8. IP-Port-Alloc TLV The format of IP-Port-Alloc TLV is shown in Figure 11. This attribute carries IPFIX Information Element 230, "natEvent", which is a flag to indicate an action of NAT operation (refer to [IPFIX]). When the value of natEvent is "1" (Create event), it means to allocate a range of transport ports; when the value is "2", it means to deallocate a range of transports ports. For the purpose of this @@ -933,21 +933,21 @@ 2: Deallocation Reserved: 0. IP-Port-Alloc TLV MUST be included as part of the IP-Port-Range - Attribute (refer to Section 3.1.2), identified as 241.TBD2.8. + Attribute (refer to Section 3.1.2), identified as 241.6.8. 3.2.9. IP-Port-Range-Start TLV The format of IP-Port-Range-Start TLV is shown in Figure 12. This attribute carries IPFIX Information Element 361, "portRangeStart", which is the smallest port number of a range of contiguous transport ports (refer to [IPFIX]). 0 1 2 3 0 1 2 3 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 @@ -966,21 +966,21 @@ Length 6 portRangeStart Integer. This field contains the data (unsigned16) of (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 - Attribute (refer to Section 3.1.2), identified as 241.TBD2.9. + Attribute (refer to Section 3.1.2), identified as 241.6.9. 3.2.10. IP-Port-Range-End TLV The format of IP-Port-Range-End TLV is shown in Figure 13. This attribute carries IPFIX Information Element 362, "portRangeEnd", which is the largest port number of a range of contiguous transport ports (refer to [IPFIX]). 0 1 2 3 0 1 2 3 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 @@ -1000,21 +1000,21 @@ 6 portRangeEnd Integer. This field contains the data (unsigned16) of (362) defined in IPFIX, right justified, and unused bits MUST be set to zero. IP-Port-Range-End TLV is included as part of the IP-Port-Range - Attribute (refer to Section 3.1.2), identified as 241.TBD2.10. + Attribute (refer to Section 3.1.2), identified as 241.6.10. 3.2.11. IP-Port-Local-Id TLV The format of IP-Port-Local-Id TLV is shown in Figure 14. This attribute carries a string called "localID", which is a local significant identifier as explained below. The primary issue addressed by this TLV is that there are CGN deployments that do not distinguish internal hosts by their internal IP address alone, but use further identifiers for unique subscriber @@ -1051,25 +1051,25 @@ string. The data type of this field is string (refer to [I-D.ietf-radext-datatypes]). This field contains the data that is a local session identifier at the customer premise, such as MAC address, interface ID, VLAN ID, PPP sessions ID, VRF ID, IP address/prefix, or another local session identifier. IP-Port-Local-Id TLV MAY be included in the following Attributes if it is necessary to identify the subscriber: - o IP-Port-Range Attribute, identified as 241.TBD2.11 (see + o IP-Port-Range Attribute, identified as 241.6.11 (see Section 3.1.2). - o IP-Port-Forwarding-Mapping Attribute, identified as 241.TBD3.11 - (see Section 3.1.3). + o IP-Port-Forwarding-Mapping Attribute, identified as 241.7.11 (see + Section 3.1.3). 4. Applications, Use Cases and Examples This section describes some applications and use cases to illustrate the use of the attributes proposed in this document. 4.1. Managing CGN Port Behavior using RADIUS In a broadband network, customer information is usually stored on a RADIUS server, and the BNG acts as a NAS. The communication between @@ -1451,37 +1451,34 @@ | | | Figure 20: RADIUS Message Flow for reporting CPE allocation/ deallocation of a port set to a visiting UE 5. Table of Attributes This document proposes three new RADIUS attributes and their formats are as follows: - o IP-Port-Limit-Info: 241.TBD1. - - o IP-Port-Range: 241.TBD2. + o IP-Port-Limit-Info: 241.5. - o IP-Port-Forwarding-Map: 241.TBD3. + o IP-Port-Range: 241.6. - Note to IANA: it is assumed that Extended-Type-1 "241" will be used - for these attributes. + o IP-Port-Forwarding-Map: 241.7. The following table provides a guide as what type of RADIUS packets that may contain these attributes, and in what quantity. Request Accept Reject Challenge Acct. # Attribute Request - 0+ 0+ 0 0 0+ TBA IP-Port-Limit-Info - 0 0 0 0 0+ TBA IP-Port-Range - 0+ 0+ 0 0 0+ TBA IP-Port-Forwarding-Map + 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.7 IP-Port-Forwarding-Map The following table defines the meaning of the above table entries. 0 This attribute MUST NOT be present in packet. 0+ Zero or more instances of this attribute MAY be present in packet. 6. Security Considerations This document does not introduce any security issue other than the ones already identified in RADIUS [RFC2865] and [RFC5176] for CoA @@ -1515,33 +1512,30 @@ place between the RADIUS client and server with communication optionally secured by IPsec or Transport Layer Security (TLS) [RFC6614]. 7. IANA Considerations This document requires new code point assignments for both IPFIX Information Elements and RADIUS attributes as explained in the following sub-sections. - It is assumed that Extended-Type-1 "241" will be used for RADIUS - attributes in Section 7.2. - 7.1. IANA Considerations on New IPFIX Information Elements The following is a new IPFIX Information Element as requested by this document (refer to Section 3.2.2) : o sourceTransportPortsLimit: * Name: sourceTransportPortsLimit. - * Element ID: TBAx1. + * Element ID: 458. * Description: This Information Element contains the maximum number of IP source transport ports that can be used by an end user when sending IP packets; each user is associated with one or more (source) IPv4 or IPv6 addresses. This IE is particularly useful in address sharing deployments that adhere to REQ-4 of [RFC6888]. Limiting the number of ports assigned to each user ensures fairness among users and mitigates the denial-of-service attack that a user could launch against other users through the address sharing device in order to grab more @@ -1561,46 +1555,54 @@ in this document be registered by the Internet Assigned Numbers Authority (IANA) from the RADIUS namespaces as described in the "IANA Considerations" section of [RFC3575], in accordance with BCP 26 [RFC5226]. For RADIUS packets, attributes and registries created by this document IANA is requested to place them at http://www.iana.org/assignments/radius-types. In particular, this document defines three new RADIUS attributes, entitled "IP-Port-Limit-Info" (see Section 3.1.1), "IP-Port-Range" (see Section 3.1.2) and "IP-Port-Forwarding-Map" (see Section 3.1.3), - with assigned values of 241.TBD1, 241.TBD2 and 241.TBD3 from the - Short Extended Space of [RFC6929]: + with assigned values of 241.5, 241.6 and 241.7 from the Short + Extended Space of [RFC6929]: Type Name Meaning ---- ---- ------- - 241.TBD1 IP-Port-Limit-Info see Section 3.1.1 - 241.TBD2 IP-Port-Range see Section 3.1.2 - 241.TBD3 IP-Port-Forwarding-Map see Section 3.1.3 + 241.5 IP-Port-Limit-Info see Section 3.1.1 + 241.6 IP-Port-Range see Section 3.1.2 + 241.7 IP-Port-Forwarding-Map see Section 3.1.3 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 - ---- ----- ------- - IP-Port-Type 1 see Section 3.2.1 - IP-Port-Limit 2 see Section 3.2.2 - IP-Port-Ext-IPv4-Addr 3 see Section 3.2.3 - IP-Port-Int-IPv4-Addr 4 see Section 3.2.4 - IP-Port-Int-IPv6-Addr 5 see Section 3.2.5 - IP-Port-Int-Port 6 see Section 3.2.6 - IP-Port-Ext-Port 7 see Section 3.2.7 - IP-Port-Alloc 8 see Section 3.2.8 - IP-Port-Range-Start 9 see Section 3.2.9 - IP-Port-Range-End 10 see Section 3.2.10 - IP-Port-Local-Id 11 see Section 3.2.11 + Value Name Definition + ----- ----- ---------- + 0 Reserved + 1 IP-Port-Type see Section 3.2.1 + 2 IP-Port-Limit see Section 3.2.2 + 3 IP-Port-Ext-IPv4-Addr see Section 3.2.3 + 4 IP-Port-Int-IPv4-Addr see Section 3.2.4 + 5 IP-Port-Int-IPv6-Addr see Section 3.2.5 + 6 IP-Port-Int-Port see Section 3.2.6 + 7 IP-Port-Ext-Port see Section 3.2.7 + 8 IP-Port-Alloc see Section 3.2.8 + 9 IP-Port-Range-Start see Section 3.2.9 + 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 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.