RADIUS Extensions for IP Port Configuration and Reporting
draft-ietf-radext-ip-port-radius-ext-00

The information below is for an old version of the document
Document Type Active Internet-Draft (radext WG)
Last updated 2014-05-09
Stream IETF
Intended RFC status (None)
Formats plain text pdf html bibtex
Stream WG state WG Document
Document shepherd None
IESG IESG state I-D Exists
Consensus Boilerplate Unknown
Telechat date
Responsible AD (None)
Send notices to (None)
Network Working Group                                           D. Cheng
Internet-Draft                                                    Huawei
Intended status: Standards Track                             J. Korhonen
Expires: November 11, 2014                                      Broadcom
                                                            M. Boucadair
                                                          France Telecom
                                                            S. Sivakumar
                                                           Cisco Systems
                                                            May 10, 2014

       RADIUS Extensions for IP Port Configuration and Reporting
                draft-ietf-radext-ip-port-radius-ext-00

Abstract

   This document defines three new RADIUS attributes.  For device 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, NAT64, Provider WiFi Gateway, etc.

   This document does not make any assumption about the deployment
   context.

Requirements Language

   The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
   "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this
   document are to be interpreted as described in RFC 2119 [RFC2119].

Status of This Memo

   This Internet-Draft is submitted in full conformance with the
   provisions of BCP 78 and BCP 79.

   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 November 11, 2014.

Cheng, et al.           Expires November 11, 2014               [Page 1]
Internet-Draft        RADIUS Extensions for IP Port             May 2014

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
   carefully, as they describe your rights and restrictions with respect
   to this document.  Code Components extracted from this document must
   include Simplified BSD License text as described in Section 4.e of
   the Trust Legal Provisions and are provided without warranty as
   described in the Simplified BSD License.

Table of Contents

   1.  Introduction  . . . . . . . . . . . . . . . . . . . . . . . .   2
   2.  Terminology . . . . . . . . . . . . . . . . . . . . . . . . .   4
   3.  RADIUS Attributes . . . . . . . . . . . . . . . . . . . . . .   5
     3.1.  Extended-Type for IP-Port-Type  . . . . . . . . . . . . .   5
     3.2.  IP-Port-Limit Attribute . . . . . . . . . . . . . . . . .   7
     3.3.  IP-Port-Range Attribute . . . . . . . . . . . . . . . . .   8
     3.4.  IP-Port-Forwarding-Map Attribute  . . . . . . . . . . . .  10
   4.  Applications, Use Cases and Examples  . . . . . . . . . . . .  12
     4.1.  Managing CGN Port Behavior using RADIUS . . . . . . . . .  12
       4.1.1.  Configure IP Port Limit for a User  . . . . . . . . .  13
       4.1.2.  Report IP Port Allocation/De-allocation . . . . . . .  15
       4.1.3.  Configure Forwarding Port Mapping . . . . . . . . . .  16
       4.1.4.  An Example  . . . . . . . . . . . . . . . . . . . . .  18
     4.2.  Report Assigned Port Set for a Visiting UE  . . . . . . .  19
   5.  Table of Attributes . . . . . . . . . . . . . . . . . . . . .  20
   6.  Security Considerations . . . . . . . . . . . . . . . . . . .  21
   7.  IANA Considerations . . . . . . . . . . . . . . . . . . . . .  21
   8.  Acknowledgements  . . . . . . . . . . . . . . . . . . . . . .  22
   9.  References  . . . . . . . . . . . . . . . . . . . . . . . . .  22
     9.1.  Normative References  . . . . . . . . . . . . . . . . . .  22
     9.2.  Informative References  . . . . . . . . . . . . . . . . .  22
   Authors' Addresses  . . . . . . . . . . . . . . . . . . . . . . .  23

1.  Introduction

   In a broadband network, customer information is usually stored on a
   RADIUS server [RFC2865] and at the time when a user initiates an IP
   connection request, the RADIUS server will populate the user's
   configuration information to the Network Access Server (NAS), which
Show full document text