Re: IETF: SixXS is shutting down

"Song Linjian (Davey)" <songlinjian@gmail.com> Mon, 27 March 2017 05:32 UTC

Return-Path: <songlinjian@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 EF6BD1274D0 for <ipv6@ietfa.amsl.com>; Sun, 26 Mar 2017 22:32:02 -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 t62pOi8mg1xY for <ipv6@ietfa.amsl.com>; Sun, 26 Mar 2017 22:32:01 -0700 (PDT)
Received: from mail-it0-x231.google.com (mail-it0-x231.google.com [IPv6:2607:f8b0:4001:c0b::231]) (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 1E67B1293F2 for <ipv6@ietf.org>; Sun, 26 Mar 2017 22:31:59 -0700 (PDT)
Received: by mail-it0-x231.google.com with SMTP id 190so40947131itm.0 for <ipv6@ietf.org>; Sun, 26 Mar 2017 22:31:59 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=from:message-id:mime-version:subject:date:in-reply-to:cc:to :references; bh=v/JFwxYZMAOKN7HQ6EaPDWCTuIt9gTFY8wZS6nbbldA=; b=U1Ed1Lmgi4FSaccj8cfBgSTYxAbhKCQZBpg9KaY/w752sGlCd2pPJPRzxJu1GlJBzk XVZXG3zQHmpLrVMx2MvSalZgfIHLa5fcVU7yNY955lytlp66dx2op7AQCSYvsZdkh1v9 +2jtvqgfQhq3LRvkclur4+A4ZavO9Y647MKzh2sOZfK9Rp0/gYacSsdNEmEr9+HbSNeW L4uyU2kPogzWSLfu63IH97rZqDlEuQHeqrEaegpOFWbU3/Ds2TrxUhKoordIlfMphupV osfG3yy/6abhYwbvqOLQ7MchhM61hJIEvCvDSs9YOdeVjx35CFNUJG0//zllp8op/luG c2dg==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:from:message-id:mime-version:subject:date :in-reply-to:cc:to:references; bh=v/JFwxYZMAOKN7HQ6EaPDWCTuIt9gTFY8wZS6nbbldA=; b=JJVkSLOl5+jVh+VE7eZZIMbiJMAsI2sDGEXVNU//JQYcidrAmoJCLJWJyhONPqJMEo I2Xf83kv4sOuAuXiqKZHry7gQq0jBmXrC5/LRnkhSwHUWQ/dTwqDS2tp7lVcD3ULRqWz Rs1JUzDL4rDXeyrnHt2UKWsvA4b/QIGhWIleN+AqI41YU4Sor/d6E8UbKJYMNMl9FwTs R7Rc2Rlln1LSOoMBT83rcNlDRbMLmbFpMW99aYh8JcgT6IqnOFfQZGZyrSl0nlQtlJEF tTBJ98jus0+U/3jDh96aVO55s1/h6zDJ/iQ7L/tijxGvmmRc6rWUKN1/TKuzZgZc27CD Zp9w==
X-Gm-Message-State: AFeK/H3sqoi43I83pJQBNf1hMFGzAOgsbhoeaKO9ttGp5ZV1jASoBeKUQGTNEIbIwbTqZg==
X-Received: by 10.107.23.6 with SMTP id 6mr19049766iox.14.1490592718414; Sun, 26 Mar 2017 22:31:58 -0700 (PDT)
Received: from [10.0.8.58] ([66.71.229.5]) by smtp.gmail.com with ESMTPSA id r30sm5161830ioi.56.2017.03.26.22.31.57 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Sun, 26 Mar 2017 22:31:57 -0700 (PDT)
From: "Song Linjian (Davey)" <songlinjian@gmail.com>
Message-Id: <A15D2326-5A29-4F47-9934-3CDF01496AA0@gmail.com>
Content-Type: multipart/alternative; boundary="Apple-Mail=_3D53D218-0DFF-44E0-92B3-A71FCE620255"
Mime-Version: 1.0 (Mac OS X Mail 10.2 \(3259\))
Subject: Re: IETF: SixXS is shutting down
Date: Mon, 27 Mar 2017 00:31:55 -0500
In-Reply-To: <CAL9jLaaRNGSgYS2VAQBoeZYAQAsdkgoiRZj8UXHZwiEsf_VN-Q@mail.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>
To: Christopher Morrow <christopher.morrow@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>
X-Mailer: Apple Mail (2.3259)
Archived-At: <https://mailarchive.ietf.org/arch/msg/ipv6/CbuogcDRjxVR1KvN8M2tTNDsN7Y>
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 05:32:03 -0000

> 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. 

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).  

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.

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!!!). 

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.

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 : ) 

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

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