Re: [v6ops] reclassify 464XLAT as standard instead of info

Gert Doering <gert@space.net> Thu, 21 September 2017 13:52 UTC

Return-Path: <gert@space.net>
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 2101913307E for <v6ops@ietfa.amsl.com>; Thu, 21 Sep 2017 06:52:44 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.6
X-Spam-Level:
X-Spam-Status: No, score=-2.6 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_LOW=-0.7] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 2jlksHqMWWZT for <v6ops@ietfa.amsl.com>; Thu, 21 Sep 2017 06:52:37 -0700 (PDT)
Received: from mobil.space.net (mobil.space.net [195.30.115.67]) (using TLSv1 with cipher ECDHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 4ADA01321C7 for <v6ops@ietf.org>; Thu, 21 Sep 2017 06:52:36 -0700 (PDT)
X-Original-To: v6ops@ietf.org
Received: from mobil.space.net (localhost [IPv6:::1]) by mobil.space.net (Postfix) with ESMTP id 4E9DD40BA5 for <v6ops@ietf.org>; Thu, 21 Sep 2017 15:52:35 +0200 (CEST)
X-SpaceNet-Relay: true
X-SpaceNet-Relay: true
Received: from moebius4.space.net (moebius4.space.net [IPv6:2001:608:2:2::251]) by mobil.space.net (Postfix) with ESMTP id 390BB40B9E; Thu, 21 Sep 2017 15:52:35 +0200 (CEST)
Received: by moebius4.space.net (Postfix, from userid 1007) id 2AFAA342D2; Thu, 21 Sep 2017 15:52:35 +0200 (CEST)
Date: Thu, 21 Sep 2017 15:52:35 +0200
From: Gert Doering <gert@space.net>
To: JORDI PALET MARTINEZ <jordi.palet@consulintel.es>
Cc: v6ops@ietf.org
Message-ID: <20170921135235.GF45648@Space.Net>
References: <376bfd13-8f22-3255-0f3b-d077cc205cc9@gmail.com> <CAKD1Yr1V5BsrrEO68ASS1hF-Qj3Q_SsyquXeRx0gNRdNURcKsw@mail.gmail.com> <55371780-be6c-49e6-fe40-bf3b4c05fcfd@gmail.com> <alpine.DEB.2.20.1709211030060.29378@uplift.swm.pp.se> <bd4c7462-2483-b617-e64c-b5dcfc768e17@gmail.com> <78CED789-6366-4CE0-8CC9-E630B13F743C@consulintel.es> <dbac4f8a-55e0-345b-667c-937b75869890@gmail.com> <F8A62D88-6FAE-48A1-A28F-F84451F781BA@consulintel.es> <f26447b3-8d9b-2216-495e-59413e3a8913@gmail.com> <0DD8E948-A2B3-46B9-9FF7-DA9A83503BBA@consulintel.es>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Disposition: inline
In-Reply-To: <0DD8E948-A2B3-46B9-9FF7-DA9A83503BBA@consulintel.es>
X-NCC-RegID: de.space
User-Agent: Mutt/1.8.2 (2017-04-18)
Archived-At: <https://mailarchive.ietf.org/arch/msg/v6ops/dBLMbxS-8sbK2XmSFCtmwQv2E4E>
Subject: Re: [v6ops] reclassify 464XLAT as standard instead of info
X-BeenThere: v6ops@ietf.org
X-Mailman-Version: 2.1.22
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: <https://mailarchive.ietf.org/arch/browse/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: Thu, 21 Sep 2017 13:52:44 -0000

Hi,

On Thu, Sep 21, 2017 at 10:40:17AM -0300, JORDI PALET MARTINEZ wrote:
> I also see a valid case for having 2 APNs. 1) for LTE broadband routers that require more than a /64 (and thus DHCPv6-PD), and 2) for the rest that are regular UEs and only require a /64 (64share for the tethering)

The claim that you need multiple APNs for that is not logical.

The basic function "assign a /64 for each PDP" is 3GPP standard, any APN
needs to do that (and that's the /64 you use for 64share).

The extra function "DHCPv6-PD" is conceptually totally independent - you
need an IPv6 capable link, nothing else, and whether or not a /64 has been
assigned is not relevant for PD.  

Now, if a given *vendor* can only turn on one or the other on their gear 
is an implementation choice, and that REALLY doesn't belong here - if at
all, it's a 3GPP standardization topic ("if you add DHCPv6PD, you MUST
continue to provide a /64 for each subscriber").

Gert Doering
        -- NetMaster
-- 
have you enabled IPv6 on something today...?

SpaceNet AG                        Vorstand: Sebastian v. Bomhard
Joseph-Dollinger-Bogen 14          Aufsichtsratsvors.: A. Grundner-Culemann
D-80807 Muenchen                   HRB: 136055 (AG Muenchen)
Tel: +49 (0)89/32356-444           USt-IdNr.: DE813185279