--- 1/draft-ietf-radext-ip-port-radius-ext-01.txt 2014-12-12 06:52:27.324056902 -0800 +++ 2/draft-ietf-radext-ip-port-radius-ext-02.txt 2014-12-12 06:52:28.056074834 -0800 @@ -1,23 +1,23 @@ Network Working Group D. Cheng Internet-Draft Huawei Intended status: Standards Track J. Korhonen -Expires: December 14, 2014 Broadcom +Expires: June 15, 2015 Broadcom M. Boucadair France Telecom S. Sivakumar Cisco Systems - June 12, 2014 + December 12, 2014 RADIUS Extensions for IP Port Configuration and Reporting - draft-ietf-radext-ip-port-radius-ext-01 + draft-ietf-radext-ip-port-radius-ext-02 Abstract This document defines three new RADIUS attributes. For devices that implementing 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 CGN (Carrier Grade NAT), NAT64, Provider WLAN Gateway, etc. @@ -38,21 +38,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 December 14, 2014. + This Internet-Draft will expire on June 15, 2015. Copyright Notice Copyright (c) 2014 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 @@ -229,20 +229,24 @@ 1. IP-Port-Limit Attribute 2. IP-Port-Range Attribute 3. IP-Port-Forwarding-Map Attribute All these attributes are allocated from the RADIUS "Extended Type" code space per [RFC6929]. + [Editor's notes - A comment was received on suggestion to map Radius + TLVs to IPFIX Elements whenever possible. Authors are working on + details on this for the next revision.] + 3.1. Extended Attributes for IP Ports 3.1.1. Extended-Type and IP-Port-Type TLV This section defines a new Extended-Type and an IP-Port-Type TLV (see Figure 1). The IP port type may be one of the following: o TCP port, UDP port, and ICMP identifier @@ -1476,22 +1480,22 @@ [I-D.gundavelli-v6ops-community-wifi-svcs] 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. [I-D.ietf-softwire-lw4over6] Cui, Y., Qiong, Q., Boucadair, M., Tsou, T., Lee, Y., and I. Farrer, "Lightweight 4over6: An Extension to the DS- - Lite Architecture", draft-ietf-softwire-lw4over6-10 (work - in progress), June 2014. + Lite Architecture", draft-ietf-softwire-lw4over6-13 (work + in progress), November 2014. [I-D.miles-behave-l2nat] Miles, D. and M. Townsley, "Layer2-Aware NAT", draft- miles-behave-l2nat-00 (work in progress), March 2009. [RFC3022] Srisuresh, P. and K. Egevang, "Traditional IP Network Address Translator (Traditional NAT)", RFC 3022, January 2001. [RFC6146] Bagnulo, M., Matthews, P., and I. van Beijnum, "Stateful