Re: [v6ops] new draft: draft-cui-v6ops-lte-lw4over6

[Mikael Abrahamsson <[e-mail]>]

On Thu, 13 Feb 2014, [e-mail] wrote:

> A new draft has been posted, at 
> http://tools.ietf.org/html/draft-cui-v6ops-lte-lw4over6. Please take a 
> look at it and comment.

This document makes me very confused.

Traditionally, the eNodeB has basically done GTP-RLC (or whatever protocol 
is used on the radio layer) conversion. All the setup has been done using 
3GPP protocols.

This document proposes to use DHCPv6oDHCPv4 with the eNodeB as a *client*. 
When I read the document, I don't understand what communication is done 
within the GTP tunnel, what is done outside the tunnel, and what role the 
eNodeB has in this.

In 4 for instance:

"The architecture described here addresses a typical use case, where
    an eNodeB's uplink supports IPv6 only and a UE using IPv4 in this
    eNodeB wants to access IPv4 Internet.  The network architecture is
    shown in Figure 1.  In this scenario, the UE can only use the IPv6
    network to access IPv4 services, so IPv4 services must be configured
    over IPv6."

I don't understand this statement. It's completely possible to set up an 
GTP tunnel over IPv6, which then can carry both IPv4 and IPv6 traffic. So 
it's not problem to support UEs with IPv4, IPv6 or DS uplinks, in current 
3GPP architecture, over a pure IPv6 mobile backhaul network.

I'm very confused what problem this document tries to solve.

-- 
Mikael Abrahamsson    email: [e-mail]