DHCPv6 Options for Discovery of 464XLAT IPv6 Prefixes
draft-cui-intarea-464xlat-prefix-dhcp-00
| Document | Type | Expired Internet-Draft (individual) | |
|---|---|---|---|
| Last updated | 2015-06-28 (latest revision 2014-12-25) | ||
| Stream | (None) | ||
| Intended RFC status | (None) | ||
| Formats |
Expired & archived
plain text
xml
pdf
html
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) | ||
https://www.ietf.org/archive/id/draft-cui-intarea-464xlat-prefix-dhcp-00.txt
Abstract
464XLAT provides limited IPv4 connectivity across an IPv6-only network using translation technology. The customer-side translator (CLAT) performs stateless 1:1 mapping of an IPv4 destination address into a provider-side translator (PLAT) IPv6 prefix, which subsequently translates it back into IPv4. Different PLATs will likely have different IPv6 prefixes, to attract traffic to the correct PLAT. Thus, an automatic PLAT-side prefix discovery method is necessary for CLATs. This document defines a DHCPv6-based method to inform a CLAT of a PLAT's IPv6 prefix and the IPv4 prefixes it serves.
Authors
Yong Cui
(yong@csnet1.cs.tsinghua.edu.cn)
Lishan Li
(lilishan9248@126.com)
Cong Liu
(gnocuil@gmail.com)
Jianping Wu
(jianping@cernet.edu.cn)
Fred Baker
(fred@cisco.com)
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)