[radext] [IANA #935820] Protocol Action: 'RADIUS Extensions for IP Port Configuration and Reporting' to Proposed Standard (draft-ietf-radext-ip-port-radius-ext-16.txt)

["Amanda Baber via RT" <[e-mail]>]

Dear Authors:

ATTENTION: A RESPONSE TO THIS MESSAGE IS NEEDED 

We've completed the registry actions for the following RFC-to-be:

draft-ietf-radext-ip-port-radius-ext-16 

ACTION 1:

The IANA Services Operator has added the following entry to the IPFIX Information Elements registry:

Element ID: 458	
Name: sourceTransportPortsLimit
Data Type: unsigned16
Data Type Semantics: totalCounter
Status: current
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 ports.
Units: ports
Range: 1-65535
Requester: [RFC-ietf-radext-ip-port-radius-ext-16]
Revision: 0
Date: 2016-11-10 

Please see
http://www.iana.org/assignments/ipfix


ACTION 2:

We've added the following entries to the Radius Attribute Types registry:

241.5    IP-Port-Limit-Info    [RFC-ietf-radext-ip-port-radius-ext-16, Section 3.1.1]
241.6    IP-Port-Range    [RFC-ietf-radext-ip-port-radius-ext-16, Section 3.1.2]
241.7    IP-Port-Forwarding-Map    [RFC-ietf-radext-ip-port-radius-ext-16, Section 3.1.3]

Please see
http://www.iana.org/assignments/radius-types


ACTION 3:

We've created the following registry under the "Radius Types" heading:

RADIUS IP Port Configuration and Reporting TLVs
Registration Procedure(s): Standards Action
Reference: [RFC-ietf-radext-ip-port-radius-ext-16]

Value 	Description 	Reference 
0	Reserved	[RFC-ietf-radext-ip-port-radius-ext-16]
1	IP-Port-Type	[RFC-ietf-radext-ip-port-radius-ext-16, Section 3.2.1]
2	IP-Port-Limit	[RFC-ietf-radext-ip-port-radius-ext-16, Section 3.2.2]
3	IP-Port-Ext-IPv4-Addr	[RFC-ietf-radext-ip-port-radius-ext-16, Section 3.2.3]
4	IP-Port-Int-IPv4-Addr	[RFC-ietf-radext-ip-port-radius-ext-16, Section 3.2.4]
5	IP-Port-Int-IPv6-Addr	[RFC-ietf-radext-ip-port-radius-ext-16, Section 3.2.5]
6	IP-Port-Int-Port	[RFC-ietf-radext-ip-port-radius-ext-16, Section 3.2.6]
7	IP-Port-Ext-Port	[RFC-ietf-radext-ip-port-radius-ext-16, Section 3.2.7]
8	IP-Port-Alloc	[RFC-ietf-radext-ip-port-radius-ext-16, Section 3.2.8]
9	IP-Port-Range-Start	[RFC-ietf-radext-ip-port-radius-ext-16, Section 3.2.9]
10	IP-Port-Range-End	[RFC-ietf-radext-ip-port-radius-ext-16, Section 3.2.10]
11	IP-Port-Local-Id	[RFC-ietf-radext-ip-port-radius-ext-16, Section 3.2.11]
12-155	Unassigned

Please see
http://www.iana.org/assignments/radius-types


The updated list of Protocol Registries is available here:
 
http://www.iana.org/protocols/

Please let us know whether the above registry actions have been completed correctly. As soon as we receive your confirmation, we'll notify the RFC Editor that this document's actions are complete. If the document has a team of authors, one reply on behalf of everyone will suffice.

Since you'll be uploading the new version of the document shortly (the new values can be added to that version before you upload), please let us know when this is available to link to.

We'll make any further reference updates in the registries when the RFC Editor notifies us that they've assigned an RFC number.

Best regards,

Amanda Baber
Lead IANA Services Specialist
PTI