IETF Logo Mail Archive

Re: [Openv6] Openv6 Bar BoF sheduling

"Liushucheng (Will)" <liushucheng@huawei.com> Thu, 13 February 2014 06:48 UTC

Return-Path: <liushucheng@huawei.com>
X-Original-To: openv6@ietfa.amsl.com
Delivered-To: openv6@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B02E01A011B for <openv6@ietfa.amsl.com>; Wed, 12 Feb 2014 22:48:14 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.298
X-Spam-Level:
X-Spam-Status: No, score=-2.298 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, MIME_CHARSET_FARAWAY=2.45, RCVD_IN_DNSWL_MED=-2.3, RP_MATCHES_RCVD=-0.548, SPF_PASS=-0.001] 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 2dk64R_tIOuc for <openv6@ietfa.amsl.com>; Wed, 12 Feb 2014 22:48:10 -0800 (PST)
Received: from lhrrgout.huawei.com (lhrrgout.huawei.com [194.213.3.17]) by ietfa.amsl.com (Postfix) with ESMTP id 59D031A011A for <openv6@ietf.org>; Wed, 12 Feb 2014 22:48:09 -0800 (PST)
Received: from 172.18.7.190 (EHLO lhreml204-edg.china.huawei.com) ([172.18.7.190]) by lhrrg01-dlp.huawei.com (MOS 4.3.7-GA FastPath queued) with ESMTP id BDN70724; Thu, 13 Feb 2014 06:48:07 +0000 (GMT)
Received: from LHREML403-HUB.china.huawei.com (10.201.5.217) by lhreml204-edg.china.huawei.com (172.18.7.223) with Microsoft SMTP Server (TLS) id 14.3.158.1; Thu, 13 Feb 2014 06:46:57 +0000
Received: from SZXEMA409-HUB.china.huawei.com (10.82.72.41) by lhreml403-hub.china.huawei.com (10.201.5.217) with Microsoft SMTP Server (TLS) id 14.3.158.1; Thu, 13 Feb 2014 06:47:51 +0000
Received: from SZXEMA509-MBS.china.huawei.com ([169.254.2.102]) by SZXEMA409-HUB.china.huawei.com ([10.82.72.41]) with mapi id 14.03.0158.001; Thu, 13 Feb 2014 14:47:42 +0800
From: "Liushucheng (Will)" <liushucheng@huawei.com>
To: "Zhouqian (Cathy)" <cathy.zhou@huawei.com>, "openv6@ietf.org" <openv6@ietf.org>
Thread-Topic: Openv6 Bar BoF sheduling
Thread-Index: AQHPKG+VftpJMtuO4UmJ5x3Qlc+T35qyN2eAgACGX9A=
Date: Thu, 13 Feb 2014 06:47:42 +0000
Message-ID: <C9B5F12337F6F841B35C404CF0554ACB5FE70159@SZXEMA509-MBS.china.huawei.com>
References: <C9B5F12337F6F841B35C404CF0554ACB5FE6A1CF@SZXEMA509-MBS.china.huawei.com> <000401cf1be4$302cf5a0$9086e0e0$@cernet.edu.cn> <C9B5F12337F6F841B35C404CF0554ACB5FE7005F@SZXEMA509-MBS.china.huawei.com> <A6A061BEE5DDC94A9692D9D81AF776DF3A4DEAE0@SZXEMA512-MBX.china.huawei.com>
In-Reply-To: <A6A061BEE5DDC94A9692D9D81AF776DF3A4DEAE0@SZXEMA512-MBX.china.huawei.com>
Accept-Language: en-US, zh-CN
Content-Language: zh-CN
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [10.66.78.79]
Content-Type: multipart/alternative; boundary="_000_C9B5F12337F6F841B35C404CF0554ACB5FE70159SZXEMA509MBSchi_"
MIME-Version: 1.0
X-CFilter-Loop: Reflected
Subject: Re: [Openv6] Openv6 Bar BoF sheduling
X-BeenThere: openv6@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: Openv6 discussion list <openv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/openv6>, <mailto:openv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/openv6/>
List-Post: <mailto:openv6@ietf.org>
List-Help: <mailto:openv6-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/openv6>, <mailto:openv6-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 13 Feb 2014 06:48:15 -0000

Hi Cathy,

Yes. Thanks for your reminding. That’s the phrase I was meaning.

Regards,
Shucheng (Will)

From: Zhouqian (Cathy)
Sent: Thursday, February 13, 2014 2:46 PM
To: Liushucheng (Will); openv6@ietf.org
Subject: 答复: Openv6 Bar BoF sheduling

Hi Will,
I think you means a side meeting.

Cathy

发件人: Openv6 [mailto:openv6-bounces@ietf.org] 代表 Liushucheng (Will)
发送时间: 2014年2月13日 11:57
收件人: openv6@ietf.org<mailto:openv6@ietf.org>
主题: [Openv6] Openv6 Bar BoF sheduling

Folks,

Let’s have a Bar BoF in London to discuss the PS and use case, and what’s next step for this work.

If you are interest, please reply to this email or click in doodle (http://doodle.com/pb3n9abm7w2gbdsp) to feedback the slot that works for you, thanks.

Regards,
Shucheng (Will)

From: Liushucheng (Will) [mailto:liushucheng@huawei.com]
Sent: Monday, January 27, 2014 4:16 PM
To: openv6@ietf.org<mailto:openv6@ietf.org>
Subject: Starting discussion

(Sorry for duplicated mails.)

Hello,

Thanks for joining the Open IPv6 (openv6) mailing list. It’s great to see so much interest in the topic!

The following questions are listed to be discussed here:
(1) What are the problems and use cases existing in various IPv6 applications, e.g., multiple IPv6 transition technologies co-exist?
(2) How to enable the applications to program the equipment to tunnel IPv6 traffic across an IPv4 data plane?
(3) How this work can be done through a general interface, e.g., to incorporate the transition policies, simplifying the different stages through the transition and guaranteeing that current decisions do not imply a complicated legacy in the future?
(4) How to make the end-to-end configuration of devices: concentrator/CGN, CPE and the provisioning system?
(5) How to extend the existing IETF protocols, e.g., netconf, to support this open interface?

In addition to the above questions, we've laid out an initial description of the problem in https://datatracker.ietf.org/doc/draft-sun-openv6-problem-statement/ and are looking for productive discussion and feedback on this list. We are now modifying it and a new version will be released accordingly. :)

Regards,
Shucheng LIU (Will)
-----------------------------------------------------------------------------------
Shucheng LIU (Will), Ph.D.
Researcher & Standard Representative
Huawei Technologies Co.,Ltd
liushucheng@huawei.com<mailto:liushucheng@huawei.com>
http://www.linkedin.com/in/shucheng
-----------------------------------------------------------------------------------

v2.23.0 | Report a Bug | By Email