IETF Logo Mail Archive

Re: IETF: SixXS is shutting down

Christopher Morrow <christopher.morrow@gmail.com> Sun, 26 March 2017 22:06 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 A64E51296ED for <ipv6@ietfa.amsl.com>; Sun, 26 Mar 2017 15:06:49 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.699
X-Spam-Level:
X-Spam-Status: No, score=-2.699 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, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001] autolearn=ham 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 VOAtR2tY_X0c for <ipv6@ietfa.amsl.com>; Sun, 26 Mar 2017 15:06:48 -0700 (PDT)
Received: from mail-qk0-x234.google.com (mail-qk0-x234.google.com [IPv6:2607:f8b0:400d:c09::234]) (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 1BD5F1296E5 for <ipv6@ietf.org>; Sun, 26 Mar 2017 15:06:48 -0700 (PDT)
Received: by mail-qk0-x234.google.com with SMTP id p22so25235460qka.3 for <ipv6@ietf.org>; Sun, 26 Mar 2017 15:06:48 -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=S6aYagEJaUvcXkgCrcM7pcy/wOEd4jNj2+BWVSyVmOQ=; b=Tn/lB3nUF1doUqH0IFhPJuyXePEXwOD7wAhQbdwLViTKT9uvWApbvp8Thv3VGYaqXk xqQzl4cn61mqRZJuRuJEtCoD/lP6wUmeF7vEkZb9enU73XA3sMIBIcLsn0g8eWdXz7ec e+5U8gxZTzt7b1nyIyUUwZDcKWWpJEqKKO3mZrgTh+F+3nYun8SpRkQQ9MRkdgY24Jwi ynUTOfFuKzMJNNLTXjIA3L8cPxwFThXKPcqmCOMg+TIsI8II0LQisVb7ozUjwHy+Ywoj GedU8/gFCf+GUO3BAdbVCfZrFHeVa+W5EymqjE4lB42tXTqMwRTcKXA7W4N12LDn3iY6 B6ig==
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=S6aYagEJaUvcXkgCrcM7pcy/wOEd4jNj2+BWVSyVmOQ=; b=hoiup8XJNSTa7UBUksRKVuSOThkx5Br19vuxFhAMXVyQS5pWWPbtaLgAOZ9CnnYQe9 Vd92ny7T4sSHX8NSaa3t2vwM3Wl3PpD6G1FD7gJV81J1aSlHKkm/W4+ehOdz/sjRQfwT Vmpurn6bdbH5fiBNJ3wG644gg0iesHiOis8vjTfUkcIWegO+8xeT6lnMUHSecGh1XIex gFoxG/+fY/SYVYw1M6Cab7SYVD9Hd7Pz1v55zWmxG+Rj/Sp6WbUvI5O+fInDxtvynyBd FgAmsY9WfBMUnJgGI9/cd8L/AebFUeu7+EqxBc5Ua4Xru+QGdtuywnbKTlEn2Bok4gQc Uheg==
X-Gm-Message-State: AFeK/H269wck/yTL0acLs6RHkgvvrqXV26P9xaQewgaK8i60rSW8hhj/SyNfdu2WCVpkL0bwP/wXbxTv6R03jg==
X-Received: by 10.55.4.146 with SMTP id 140mr18563634qke.23.1490566007323; Sun, 26 Mar 2017 15:06:47 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.140.17.75 with HTTP; Sun, 26 Mar 2017 15:06:46 -0700 (PDT)
In-Reply-To: <C9250641-C273-4489-9C7D-D467667529BD@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>
From: Christopher Morrow <christopher.morrow@gmail.com>
Date: Sun, 26 Mar 2017 18:06:46 -0400
Message-ID: <CAL9jLaaRNGSgYS2VAQBoeZYAQAsdkgoiRZj8UXHZwiEsf_VN-Q@mail.gmail.com>
Subject: Re: IETF: SixXS is shutting down
To: Song Linjian <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="001a114c9c7a618591054ba971ee"
Archived-At: <https://mailarchive.ietf.org/arch/msg/ipv6/XvCwNqAA-_dTnpHC7ri3hYnOxKQ>
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: Sun, 26 Mar 2017 22:06:49 -0000

On Sun, Mar 26, 2017 at 4:23 PM, Song Linjian <songlinjian@gmail.com> wrote:

> Chicken and egg problem is the same :
>
> ISP complains there is no content in IPv6, no requirement from user for
> IPv6 connection. ICP complains there is no IPv6 network and IPv6 user
>
> China is different from India because it can not leap by taking the
> advantage of IPv6 development of big global ICPs, like Google , Facebook,
> and Youtube. Besides, most netizens in China do not consume much content in
> English. Most
>

some of those ICP are blocked... of course.
Some of them actually do offer local ipv6 versions of their content...
Some of them actually do offer local-language support over the ipv6 even.

Some of the tunnel users in question are probably trying to aboice the
blocks mentioned, right?
ISPs probably can't really enable bypassing filtering, not without
hand-slaps from the larger gov't anyway.


> of people can live well without connections outside. So the only hope is
> on the local ICP like Baidu , Tencent and Alibaba. But the local ICP and
> ISP are in the early stage of Chicken and egg problem.
>
>
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 :(

v2.23.0 | Report a Bug | By Email