Re: [v6ops] Need ref to 3GPP spec for the use of DHCPv6 Prefix Delegation, e.g. for smartphone tethering

Vízdal Aleš <ales.vizdal@t-mobile.cz> Tue, 08 October 2013 08:49 UTC

Return-Path: <ales.vizdal@t-mobile.cz>
X-Original-To: v6ops@ietfa.amsl.com
Delivered-To: v6ops@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6ABB321E8187 for <v6ops@ietfa.amsl.com>; Tue, 8 Oct 2013 01:49:24 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.89
X-Spam-Level:
X-Spam-Status: No, score=-0.89 tagged_above=-999 required=5 tests=[AWL=0.060, BAYES_00=-2.599, HELO_EQ_CZ=0.445, HOST_EQ_CZ=0.904, MIME_8BIT_HEADER=0.3]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id N1zF9iw96pRC for <v6ops@ietfa.amsl.com>; Tue, 8 Oct 2013 01:49:18 -0700 (PDT)
Received: from ctxmailhub.t-mobile.cz (ctxmailhub.t-mobile.cz [93.153.104.87]) by ietfa.amsl.com (Postfix) with ESMTP id 5D4FE21E8185 for <v6ops@ietf.org>; Tue, 8 Oct 2013 01:49:13 -0700 (PDT)
Received: from srvhk504.rdm.cz (unknown [10.254.92.81]) by ctxmailhub.t-mobile.cz (Postfix) with ESMTP id 6AD1A2E09A8; Tue, 8 Oct 2013 10:49:12 +0200 (CEST)
Received: from SRVHKE02.rdm.cz ([fe80::94ce:8456:f6fa:86a8]) by srvhk504.rdm.cz ([::1]) with mapi; Tue, 8 Oct 2013 10:49:11 +0200
From: Vízdal Aleš <ales.vizdal@t-mobile.cz>
To: Alexandru Petrescu <alexandru.petrescu@gmail.com>, "Rajiv Asati (rajiva)" <rajiva@cisco.com>, Mikael Abrahamsson <swmike@swm.pp.se>
Date: Tue, 08 Oct 2013 10:49:04 +0200
Thread-Topic: [v6ops] Need ref to 3GPP spec for the use of DHCPv6 Prefix Delegation, e.g. for smartphone tethering
Thread-Index: Ac7D+lubGOVDUXZmRxWjznDvEvmbKwABm/ZQ
Message-ID: <1808340F7EC362469DDFFB112B37E2FCD877245410@SRVHKE02.rdm.cz>
References: <B14A62A57AB87D45BB6DD7D9D2B78F0B2AB673CE@xmb-rcd-x06.cisco.com> <5252C5C2.5080706@gmail.com> <1808340F7EC362469DDFFB112B37E2FCD87724529F@SRVHKE02.rdm.cz> <5252DCEF.6030705@gmail.com> <1808340F7EC362469DDFFB112B37E2FCD87724530A@SRVHKE02.rdm.cz> <5252E66D.3080005@gmail.com> <1808340F7EC362469DDFFB112B37E2FCD87724531C@SRVHKE02.rdm.cz> <5253B80E.7030008@gmail.com>
In-Reply-To: <5253B80E.7030008@gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
acceptlanguage: en-US
Content-Type: text/plain; charset="iso-8859-2"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-CFilter-Loop: Forwarded
Cc: "v6ops@ietf.org" <v6ops@ietf.org>
Subject: Re: [v6ops] Need ref to 3GPP spec for the use of DHCPv6 Prefix Delegation, e.g. for smartphone tethering
X-BeenThere: v6ops@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: v6ops discussion list <v6ops.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/v6ops>, <mailto:v6ops-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/v6ops>
List-Post: <mailto:v6ops@ietf.org>
List-Help: <mailto:v6ops-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/v6ops>, <mailto:v6ops-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 08 Oct 2013 08:49:24 -0000

> > The GGSN/PGW is UEs next-hop as the traffic is tunnelled in GTP
> > through all the intermediate nodes.
> 
> Ah, right, there is a GTP tunnel above all the intermediary IP nodes.
> 
> However, even when a tunnel is dynamically set up, a routing table entry is added in
> the Relay's routing table (or other similar entry).  The parameters of that entry
> necessarily include, among others, the prefix which is allocated.
> 
> No?

The tunnel stays up for the lifetime of the PDP/PDN context. There is no relay in the 3GPP access
architecture. If the tunnel drops the PGW/GGSN will remove the route from their routing table,
once a new tunnel is setup the routing table is updated accordingly.

> Alex

Ales