Radius Extension for Lightweight 4over6
draft-sun-softwire-lw4over6-radius-00

Document Type Expired Internet-Draft (individual)
Authors Jianping Wu  , Qi Sun  , ZiLong Liu 
Last updated 2014-08-18 (latest revision 2014-02-14)
Stream (None)
Intended RFC status (None)
Formats
Expired & archived
pdf htmlized bibtex
Stream Stream state (No stream defined)
Consensus Boilerplate Unknown
RFC Editor Note (None)
IESG IESG state Expired
Telechat date
Responsible AD (None)
Send notices to (None)

This Internet-Draft is no longer active. A copy of the expired Internet-Draft can be found at
https://www.ietf.org/archive/id/draft-sun-softwire-lw4over6-radius-00.txt

Abstract

IPv4-over-IPv6 tunneling transition mechanisms provide both IPv4 and IPv6 connectivity services simultaneously during the IPv4/IPv6 co- existing period. The Dynamic Host Configuration Protocol for IPv6(DHCPv6) options has been extended and defined to configure tunnel initiator (TI) in lightweight 4over6. However, in many networks, the configuration information are stored in Authentication Authorization and Accounting (AAA) servers while user configuration is mainly from Broadband Network Gateway (BNG) through DHCPv6 protocol. Thus AAA server as a database can be extended to establish and store the whole information of tunnels and help the tunnel concentrator (TC) recover in failure. This document defines the mechanism and the Remote Authentication Dial In User Service (RADIUS) attributes that carry TI configuration information from AAA server to BNG and the tunnel configuration information from AAA server to TC.

Authors

Jianping Wu (jianping@cernet.edu.cn)
Qi Sun (sunqi@csnet1.cs.tsinghua.edu.cn)
ZiLong Liu (liuzilong8266@126.com)

(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)