--- 1/draft-ietf-radext-ip-port-radius-ext-10.txt	2016-08-10 19:15:52.124092884 -0700
+++ 2/draft-ietf-radext-ip-port-radius-ext-11.txt	2016-08-10 19:15:52.192094583 -0700
@@ -1,23 +1,23 @@
 
 Network Working Group                                           D. Cheng
 Internet-Draft                                                    Huawei
 Intended status: Standards Track                             J. Korhonen
-Expires: January 29, 2017                           Broadcom Corporation
+Expires: February 11, 2017                          Broadcom Corporation
                                                             M. Boucadair
                                                                   Orange
                                                             S. Sivakumar
                                                            Cisco Systems
-                                                           July 28, 2016
+                                                         August 10, 2016
 
        RADIUS Extensions for IP Port Configuration and Reporting
-                draft-ietf-radext-ip-port-radius-ext-10
+                draft-ietf-radext-ip-port-radius-ext-11
 
 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 TCP/UDP ports
    and ICMP identifiers, 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.
 
@@ -35,21 +35,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 January 29, 2017.
+   This Internet-Draft will expire on February 11, 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
@@ -1457,34 +1457,39 @@
    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 are code point assignments for new IPFIX Information
    Elements as requested by this document:
 
    o  transportType (refer to Section 3.2.1): The identifier of this
       IPFIX Information Element is TBAx1.  The data type of this IPFIX
-      Information Element is unsigned8, and the Element's value
-      indicates TCP/UDP ports and ICMP Identifiers (1), TCP/UDP ports
-      (2), TCP ports (3), UDP ports (4) or ICMP identifiers (5).
+      Information Element is unsigned8, the data type semantics is
+      identifier, the data unit is null, and the data value range is 1
+      to 5 inclusively.  The Element's value indicates TCP/UDP ports and
+      ICMP Identifiers (1), TCP/UDP ports (2), TCP ports (3), UDP ports
+      (4) or ICMP identifiers (5).
 
    o  natTransportLimit (refer to Section 3.2.2): The identifier of this
       IPFIX Information Element is TBAx2.  The data type of this IPFIX
-      Information Element is unsigned16, and the Element's value is the
-      max number of IP transport ports to be assigned to an end user
-      associated with one or more IPv4 addresses.
+      Information Element is unsigned16, the data type semantics is
+      totalCounter, the data type unit is ports, and the data value
+      range is from 1 to 65535.  The Element's value is the max number
+      of IP transport ports to be assigned to an end user associated
+      with one or more IPv4 addresses.
 
    o  localID (refer to Section 3.2.11): The identifier of this IPFIX
       Information Element is TBAx3.  The data type of this IPFIX
-      Information Element is string, and the Element's value is an IPv4
-      or IPv6 address, a MAC address, a VLAN ID, etc.
+      Information Element is string, the data type semantics is default,
+      the data type unit is null.  The Element's value is an IPv4 or
+      IPv6 address, a MAC address, a VLAN ID, etc.
 
 7.2.  IANA Considerations on New RADIUS Attributes
 
    The authors request that Attribute Types and Attribute Values defined
    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.