[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

RE: WG Last Call: 3GPP Analysis Document



[ post by non-subscriber.  with the massive amount of spam, it is easy to miss
  and therefore delete posts by non-subscribers.  if you wish to regularly
  post from an address that is not subscribed to this mailing list, send a
  message to <listname>-owner@ops.ietf.org and ask to have the alternate
  address added to the list of addresses from which submissions are
  automatically accepted. ]

here are some more comments on this document:

----
3.2.2 Tunneling outside the 3GPP Operator's Network 
     
    This subsection includes the case when the peer node is outside the 
    operator's network. In that case the IPv6-in-IPv4 tunnel starting 
    point can be in the operator's network - encapsulating node can be 
    e.g. the GGSN or the edge router. 
     
    The case is pretty straightforward if the upstream ISP provides 
    native IPv6 connectivity to the Internet. If there is no native 
    IPv6 connectivity available in the 3GPP network, an IPv6-in-IPv4 
    tunnel should be configured from e.g. the GGSN to the dual stack 
    border gateway in order to access the upstream ISP. 
     
    If the ISP only provides IPv4 connectivity, then the IPv6 traffic 
    initiated from the 3GPP network should be transported tunneled in 
    IPv4 to the ISP. 
     
    Usage of configured IPv6-in-IPv4 tunneling is recommended. As the 
    number of the tunnels outside of the 3GPP network is limited, no 
    more than a couple of tunnels should be needed. 
     
    ISP transition scenarios are described in [ISP-scen]. 
----     

it is somehow difficult to follow this section. there are three
important parts here: gprs access network, 3gpp ip backbone (if the 3gpp
operator has one) and upstream isp. it is hard to decide which is which
in the text.

is this what is meant or something else?

    This subsection includes the case when the peer node is outside the
    operator's network. In that case an IPv6-in-IPv4 tunnel should be
    configured in order to obtain IPv6 connectivity and reach other IPv6
nodes.

    Starting point can be in the operator's network and will depend on
how far
    the 3GPP operator has come in implementing IPv6. If the 3GPP
operator
    does not have an IP backbone or has not implemented IPv6 in the
backbone,
    the encapsulating node can be the GGSN. If the 3GPP operator does
have an
    own IP backbone, and has implemented IPv6, but upstream ISP does not
provide
    IPv6 connectivity to the Internet, the encapsulating node can be the
edge router. 
     
    The case is pretty straightforward if the upstream ISP provides 
    IPv6 connectivity to the Internet. In that case the 3GPP operator
    does not have to configure any tunnels, since the upstream ISP will
    take care of routing IPv6 packets. If the upstream ISP does not
    provide IPv6 connectivity, an IPv6-in-IPv4 tunnel should be
configured
    from e.g. the edge router to a dual stack border gateway operated by
another
    ISP which is offering IPv6 connectivity.

    Usage of configured IPv6-in-IPv4 tunneling is recommended. As the 
    number of the tunnels outside of the 3GPP network is limited, no 
    more than a couple of tunnels should be needed. 


jasminko