Subject: [BEHAVE] FW: New Version Notification for draft-cheng-behave-cgn-cfg-radius-ext-02.txt

From: Dean cheng <[email-masked]>
Date: Fri, 06 Jan 2012 04:30:20 +0000

We've just posted a new revision for the

draft-cheng-behave-cgn-cfg-radius-ext-02<http://datatracker.ietf.org/doc/draft-cheng-behave-cgn-cfg-radius-ext/>, with a few

editing corrections.

We presented this draft the first time in BEHAVE/Taipei

where the conclusion was to "take it to the list", so this

message is to encourage some discussion to see if the proposed

is useful when deploying a CGN (NAT44, NAT64) in an

access/broadband network.

The problem and the proposed solution from this draft

are as follows (for details, please refer to the draft):

Today in an access/broadband network where BNG/BRAS

(which contains a NAS component) deployed,  RADIUS

protocol is used for communication between the BNG/BRAS

and the RADIUS server, so that some user based configuration

(such as user's credential, IP address, etc.) that pre-configured

on the RADIUS server can be conveyed to the BNG/BRAS at

the time when the user signs on to the Internet service.

In deploying CGN, there would also be some individual user

based parameters (such as port limit. address/port mapping that

needs to be statically configured for port forwarding), which

needs to be made known to the CGN, which can then operate

correctly on individual traffic.

When a CGN is co-located with the BNG/BRAS, the new

configuration problem/requirement can be resolved by pre-configuring

user based CGN parameters on the RADIUS server, and those

parameters can be transferred to the CGN along with others as in today's

operation. This solution does not need new protocol or any change in

the operation, but only proposes some new RADIUS attributes

and the key advantage is the solution leverages the existing

access/broadband network's infrastructure and operation.

Note however that the proposed only aims at the deployment where the

CGN is co-located with the BNG/BRAS, which is a real case but not

always (e.g., a CGN may be deployed as a stand-alone device away from

BNG/BRAS sometimes).

Cheers

Dean

-----Original Message-----
From: [email-masked] [mailto:[email-masked]]
Sent: Thursday, January 05, 2012 5:33 PM
To: Dean cheng
Cc: Dean cheng; [email-masked]
Subject: New Version Notification for draft-cheng-behave-cgn-cfg-radius-ext-02.txt

A new version of I-D, draft-cheng-behave-cgn-cfg-radius-ext-02.txt has been successfully submitted by Dean Cheng and posted to the IETF repository.

Filename:   draft-cheng-behave-cgn-cfg-radius-ext

Revision:   02

Title:            Radius Extensions for CGN Configurations

Creation date:    2012-01-06

WG ID:            Individual Submission

Number of pages: 22

Abstract:

   This document defines new RADIUS attributes that can be used by a

   Carried Grade NAT device to communicate with a RADIUS server using

   RADIUS protocol to configure or report TCP/UDP ports and ICMP

   identifiers mapping behavior for specific Internet subscribers.

The IETF Secretariat