Re: [v6ops] Apple and IPv6, a few clarifications - 64share

Alexandru Petrescu <alexandru.petrescu@gmail.com> Mon, 22 June 2015 15:11 UTC

Return-Path: <alexandru.petrescu@gmail.com>
X-Original-To: v6ops@ietfa.amsl.com
Delivered-To: v6ops@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B0F481ACE27 for <v6ops@ietfa.amsl.com>; Mon, 22 Jun 2015 08:11:22 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.084
X-Spam-Level:
X-Spam-Status: No, score=-3.084 tagged_above=-999 required=5 tests=[BAYES_20=-0.001, DKIM_ADSP_CUSTOM_MED=0.001, FREEMAIL_FROM=0.001, HELO_EQ_FR=0.35, NML_ADSP_CUSTOM_MED=0.9, RCVD_IN_DNSWL_HI=-5, SPF_SOFTFAIL=0.665] autolearn=ham
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 28JOOalAKoqr for <v6ops@ietfa.amsl.com>; Mon, 22 Jun 2015 08:11:14 -0700 (PDT)
Received: from cirse-out.extra.cea.fr (cirse-out.extra.cea.fr [132.167.192.142]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id D6FB21ACE1B for <v6ops@ietf.org>; Mon, 22 Jun 2015 08:11:13 -0700 (PDT)
Received: from pisaure.intra.cea.fr (pisaure.intra.cea.fr [132.166.88.21]) by cirse.extra.cea.fr (8.14.2/8.14.2/CEAnet-Internet-out-2.3) with ESMTP id t5MFB7Xs011310; Mon, 22 Jun 2015 17:11:07 +0200
Received: from pisaure.intra.cea.fr (localhost [127.0.0.1]) by localhost (Postfix) with SMTP id 4D1A3202C37; Mon, 22 Jun 2015 17:14:00 +0200 (CEST)
Received: from muguet1.intra.cea.fr (muguet1.intra.cea.fr [132.166.192.6]) by pisaure.intra.cea.fr (Postfix) with ESMTP id 35AFF202B33; Mon, 22 Jun 2015 17:14:00 +0200 (CEST)
Received: from [127.0.0.1] (is227335.intra.cea.fr [10.8.34.184]) by muguet1.intra.cea.fr (8.13.8/8.13.8/CEAnet-Intranet-out-1.2) with ESMTP id t5MFB33O031222; Mon, 22 Jun 2015 17:11:07 +0200
Message-ID: <55882587.6030702@gmail.com>
Date: Mon, 22 Jun 2015 17:11:03 +0200
From: Alexandru Petrescu <alexandru.petrescu@gmail.com>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:31.0) Gecko/20100101 Thunderbird/31.7.0
MIME-Version: 1.0
To: Ross Chandler <ross@eircom.net>, Mikael Abrahamsson <swmike@swm.pp.se>
References: <E1C235B5-1421-4DAF-A2F3-F963982233DF@apple.com> <5587EFDD.6030807@gmail.com> <alpine.DEB.2.02.1506221415100.9487@uplift.swm.pp.se> <AB88C7C2-A367-4233-9214-A210E47F1507@eircom.net>
In-Reply-To: <AB88C7C2-A367-4233-9214-A210E47F1507@eircom.net>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 8bit
Archived-At: <http://mailarchive.ietf.org/arch/msg/v6ops/hWgmQEyg3XW4xaEkWnQy4B6_TZc>
Cc: v6ops@ietf.org
Subject: Re: [v6ops] Apple and IPv6, a few clarifications - 64share
X-BeenThere: v6ops@ietf.org
X-Mailman-Version: 2.1.15
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: Mon, 22 Jun 2015 15:11:22 -0000


Le 22/06/2015 14:24, Ross Chandler a écrit :
>
>> On 22 Jun 2015, at 13:16, Mikael Abrahamsson <swmike@swm.pp.se>
>> wrote:
>>
>> On Mon, 22 Jun 2015, Alexandru Petrescu wrote:
>>
>>> It is better to tell the operator to provide a /63 to
>>> smartphones (not a /64), with DHCPv6 Prefix Delegation.  That
>>> will fix it.
>>
>> DHCPv6-PD exists in recent 3GPP documents, but vendor
>> implementation of this is not wide-spread. We do *not* want to
>> gate IPv6 rollout in mobile networks on this functionality. Yes, we
>> want it, but we can’t wait for it.
>
> Agreed. Also L2 bridging and 64share can be used to simultaneously
> provide IPv6 over WiFi, Bluetooth, and wired Ethernet.

Yes, some can be bridged.

But only the bridgeable links can be bridged (802) - serial, CAN, USB,
wont bridge.

Some subnets could bridge yet won't - in order to avoid noise (safety vs
entertainment).

Some subnets route (not bridge) for scalability reasons.

Alex

>
> Ross
>