Re: IETF: SixXS is shutting down

Christopher Morrow <christopher.morrow@gmail.com> Mon, 27 March 2017 14:17 UTC

Return-Path: <christopher.morrow@gmail.com>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C82B41296A1 for <ipv6@ietfa.amsl.com>; Mon, 27 Mar 2017 07:17:32 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.999
X-Spam-Level:
X-Spam-Status: No, score=-0.999 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, FREEMAIL_REPLY=1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001] autolearn=no autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
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 RjRc4n4sX4KN for <ipv6@ietfa.amsl.com>; Mon, 27 Mar 2017 07:17:31 -0700 (PDT)
Received: from mail-qt0-x233.google.com (mail-qt0-x233.google.com [IPv6:2607:f8b0:400d:c0d::233]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id D3AC712956B for <ipv6@ietf.org>; Mon, 27 Mar 2017 07:17:30 -0700 (PDT)
Received: by mail-qt0-x233.google.com with SMTP id n21so38386269qta.1 for <ipv6@ietf.org>; Mon, 27 Mar 2017 07:17:30 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=fG5bj++dRyL7OAO6XSrW1zS5HBw16xSWVQ9XvDRgbvE=; b=Bs7X701CCnSFaQ6bHL4GWf1eYNj3AEnlTikCwLwffKagE0jEIB7dJ/XBXkGnZ01Cch zs1U5LvCh/xy24ukcfFZ9ybnT42mDAUrYpyo9xkCvE+D1IavA6vrF+5FHtEvRpy7xA1/ 2a2JUQwLY+rWUrfnrAhANWnVYzo4xzTbMBa+puPh9PiZDkFIPvYR87V+CN0s5QLEgetf EPxSaDjlmwY+lAqffcX3rBSN2W0VMSnE/XPF7HVj7C4TAGpkELt3w9EOT46OafoufavZ scjjesd1w1q75o5NCx9MDhi5oWHmswwXdZJn2MhOYWxmzaWfPER9OuK/tho/xrK2iOxe YdvA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=fG5bj++dRyL7OAO6XSrW1zS5HBw16xSWVQ9XvDRgbvE=; b=CbVZaZnJvMgYIYcSK/N+LX5xvxZpSVPqhcLbl+eaX5IIY5YnXwMSNmYfqu8OaMJCjJ P6R4yblPo45Q4hYUb/QUQ9CfMRImNVHm9UlPLnjsseXMH2m4FtAAZlNb3QQZ4fhlu0K1 XlYGYnYtYMeGH46ptI4Z4OIcCl7CKxX82S7oS/yYONNxXxsWqZVJM4+3Y2HRfYpNhePL OXU31uZ1DuX91oeo6NeBkk/lQxgU0CCnknNFZRNNwPCt+FKRT6oxIKI8euBVkG32CiNx mwOTDCv8e1AmWzD3H276/CymDxVuWBrkE7Y5WYvPsCnPiZU+hwntYVnn4WGHzY7KRIwU ajyw==
X-Gm-Message-State: AFeK/H01PMqPNLdmoMK6ji0Wqec6TbaHgso7ca8D9n3ro10mGWnMt57d+OJivZYYKsVfEAr8XgmwFVIBGeWR4Q==
X-Received: by 10.200.51.117 with SMTP id u50mr22630449qta.133.1490624249944; Mon, 27 Mar 2017 07:17:29 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.140.17.75 with HTTP; Mon, 27 Mar 2017 07:17:29 -0700 (PDT)
In-Reply-To: <A15D2326-5A29-4F47-9934-3CDF01496AA0@gmail.com>
References: <CAEnbrFn=10nmSwDCT+hwMzVOkAcX7TpZwM=YNi_=smnY=LUrgA@mail.gmail.com> <70EDF6B4-CCFB-45BE-A377-8EBD1C899231@gmail.com> <635f4330-eae5-ad47-f4d5-da1402393993@massar.ch> <C9250641-C273-4489-9C7D-D467667529BD@gmail.com> <CAL9jLaaRNGSgYS2VAQBoeZYAQAsdkgoiRZj8UXHZwiEsf_VN-Q@mail.gmail.com> <A15D2326-5A29-4F47-9934-3CDF01496AA0@gmail.com>
From: Christopher Morrow <christopher.morrow@gmail.com>
Date: Mon, 27 Mar 2017 08:17:29 -0600
Message-ID: <CAL9jLaZMsfzE_MiPtn5H_vb7R2kOGr868zXnHX3O_7xN05NNdQ@mail.gmail.com>
Subject: Re: IETF: SixXS is shutting down
To: "Song Linjian (Davey)" <songlinjian@gmail.com>
Cc: Jeroen Massar <jeroen@massar.ch>, SixXS Staff <info@sixxs.net>, IETF IPv6 Mailing List <ipv6@ietf.org>, Pim van Pelt <pim@ipng.nl>
Content-Type: multipart/alternative; boundary="001a113ace70e97b8e054bb7005c"
Archived-At: <https://mailarchive.ietf.org/arch/msg/ipv6/pc-9FHUdqjv2dVYUPxIZ2vBl_N8>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ipv6/>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 27 Mar 2017 14:17:33 -0000

On Sun, Mar 26, 2017 at 11:31 PM, Song Linjian (Davey) <
songlinjian@gmail.com> wrote:

>
> what's strange is the story ~10yrs back (more actually) that 'all isps in
> china are ipv6 enabled' isn't really true, I guess?
> sad :(
>
>
> Major ISPs are IPv6 enabled in the aspect of the backbone, not the last
> mile to users. Some of them deployed IPv6 island that is not connected to
> the backbone.
>
>
that doesn't sound like an ipv6 deployment at all. bummer.


> There are two cases I experienced last year :
>
> 1) China mobile is provisioning IPv6 to their users in Beijing over VoLTE,
> so I can receive IPv6 address in my handset. But I can not ping out (out of
> China).
>
>
I don't think you can provision ipv<anything> over 'volte' ... volte is
just: 'send voice over ip to handsets'. The LTE standard does speak
strongly about requiring ipv6 though, so probably any LTE deployment does
have ipv6 as a component.

perhaps you mean that?


> 2) The ISP in Fujian province, they deployed IPv6 to the local network. We
> once setup IPv6-only DNS servers there but we can not pull the zone from
> the master server in my lab in Beijing.
>
> Now the business of Chinese telcos are impacted by the Internet company,
> so they are not motivated to move forward and increase the investment in
> IPv6. The main force of IPv6 guys I know well are from the research
> department , not from the operational department of these telcos. The later
> has more voice in decision making from my impression.
>

and again:
  1) some of the examples you provided are not reachable in the PRC,
because of some PRC local decisions/actions
  2) all of the examples you cited (facebook, youtube, google, etc) are
ipv6 enabled for the rest of the world.
  3) some of these properties even provide content from inside the prc,
over ipv6

I am betting there are other, larger, problems with ipv6 deployment in the
PRC, related to things like: "Why can I not get to facebook.com?" while in
the PRC.


> CERNET2 is good but the example is not copied to other ISPs. IMHO academic
> guys spent too much effort on transition protocols and tools as a reward to
> intellectual challenges. few of them are really deployed in scale. Instead,
> too many IPv6 transition choices make IPv6 adoption harder for telcos
> operational people who think IPv6 is not ready for productional network.
> Even in the research area, there are different voice/noise  to hold back
> the IPv6 development, like SDN, non-ip solutions, even IPv9 (the freak!!!).
>
>
the rest of the world basically disagrees though? ipv6 deployment is moving
further and faster every day... except in the PRC, it seems?


> In policy making layer, there exists some fears and exaggerating opinions
> with non-trivial group of advocates who try to convince Gov't that IPv6 may
> introduce new threats and impacts to current censorship,like IPsec, even
> the fact that IPsec traffic is poor.
>
>
maybe don't do the censorship part then?


> In general, there are many challenges for IPv6 guys in China as far as I
> can tell. More consensus should be reached in the community to take real
> actions. The good news is that the global IPv6 traffic is reaching 18% of
> total which exerts pressures on both industry and Gov't. In most Chinese
> people‘s mind, it seems acceptable that China fall little behind U.S or EU
> in many areas, but not India and Vietnam.  More IPv6 stories of those
> countries and regions can really help by hurting the proud : )
>
>
ok


>  I’m expecting to see changes in the coming years.
>
>
terrific.


> ------------------------------
> Davey Song(宋林健)
> BII Lab
> songlinjian@gmail.com
>
>
>