Dear Gang,
On Aug 9, 2011, at 7:14 PM, GangChen wrote:
Dear Jouni,
In mobile CPE case, MT and TE are separated. That would need
additional requirements in some particular cases, e.g. dynamic IPv6
address allocation.
Separate MT TE is part of the existing 3GPP specifications. There is
Dear Jouni,
In mobile CPE case, MT and TE are separated. That would need
additional requirements in some particular cases, e.g. dynamic IPv6
address allocation.
According to the 3GPP specification, the UE shall build the link-local
address using the interface identifier provided by the PDN GW
Dear Gang,
I would be inclined to say that within the 3GPP scope the client is always the
UE and its form factor or the end usage scenario does not really matter. It
does not change the way the UE is expected to behave from the 3GPP system point
of view, unless there is a new functional
I got one comment to our draft. Section 5.4 discusses some known neighbor
discovery issues out there. I forgot to add one that I believe belongs here or
then in Section 5.2; which one I am not sure yet. In Section 5.2 it is said
that the GGSN/PGW provides an unique IID to the UE (i.e.
Hello Authors,
I think it is worth adding some texts to describe mobile CPE case, in
which CPEs with wireless modem use 3GPP access as uplink.
Gang
2011/8/2, The IESG iesg-secret...@ietf.org:
The IESG has received a request from the IPv6 Operations WG (v6ops) to
consider the following
