Qiong,
from MAP's perspective it doesn't matter if it is a /64 on the WAN or a /56
delegated prefix.
any prefix can have EA bits.
[Qiong] In theory, right. But I think it still have several issues here:
1) The /64 WAN prefix or a /56 delegated prefix does not have a flag saying
hey, I'm
Ian,
Whichever state is selected, NAT is certainly fundamental to how the state
will operate and so we tried to weave it into the functional description. I'm
not sure that provisioned NAT info enough to be able to use to unambiguously
define with operating 'mode' (for want of a better
Hi Ole,
As a background, the usual modes supported by a CPE are: IPv4-only, Dual-stack.
A natural mode to be added to the list is IPv6-only ... but this mode is not
sufficient to reflect whether IPv4 service continuity features are enabled in
the CPE or not. This draft focuses on this service:
On 12/3/12 4:55 AM, mohamed.boucad...@orange.com
mohamed.boucad...@orange.com wrote:
Hi Ole,
As a background, the usual modes supported by a CPE are: IPv4-only,
Dual-stack. A natural mode to be added to the list is IPv6-only ... but
this mode is not sufficient to reflect whether IPv4 service
Ole,
On 2012-12-3, at 下午5:06, Ole Trøan wrote:
Ian,
Whichever state is selected, NAT is certainly fundamental to how the state
will operate and so we tried to weave it into the functional description.
I'm not sure that provisioned NAT info enough to be able to use to
unambiguously
Let's get back to basics.
The encapsulation and forwarding of packets between tunnel endpoints is
supported by a combination of configuration state and mapped bits, if any.
There are 48 bits of IPv4 address+port space. You can map 0 or more of these
bits into the 128 bits of IPv6 space. The
