Re: [Openv6] Openv6 Bar BoF sheduling

"Liushucheng (Will)" <liushucheng@huawei.com> Tue, 18 February 2014 08:52 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 8981D1A009E for <openv6@ietfa.amsl.com>; Tue, 18 Feb 2014 00:52:20 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.749
X-Spam-Level:
X-Spam-Status: No, score=-4.749 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, 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 Td6QgXllOkV3 for <openv6@ietfa.amsl.com>; Tue, 18 Feb 2014 00:52:18 -0800 (PST)
Received: from lhrrgout.huawei.com (lhrrgout.huawei.com [194.213.3.17]) by ietfa.amsl.com (Postfix) with ESMTP id 0853E1A008D for <openv6@ietf.org>; Tue, 18 Feb 2014 00:52:16 -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 BDR91868; Tue, 18 Feb 2014 08:52:13 +0000 (GMT)
Received: from LHREML406-HUB.china.huawei.com (10.201.5.243) by lhreml204-edg.china.huawei.com (172.18.7.223) with Microsoft SMTP Server (TLS) id 14.3.158.1; Tue, 18 Feb 2014 08:51:52 +0000
Received: from SZXEMA409-HUB.china.huawei.com (10.82.72.41) by lhreml406-hub.china.huawei.com (10.201.5.243) with Microsoft SMTP Server (TLS) id 14.3.158.1; Tue, 18 Feb 2014 08:51:59 +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; Tue, 18 Feb 2014 16:51:55 +0800
From: "Liushucheng (Will)" <liushucheng@huawei.com>
To: Brian E Carpenter <brian.e.carpenter@gmail.com>
Thread-Topic: [Openv6] Openv6 Bar BoF sheduling
Thread-Index: AQHPKG+VftpJMtuO4UmJ5x3Qlc+T35q3zzsAgAE1DcCAAE9QAIABaCrw
Date: Tue, 18 Feb 2014 08:51:55 +0000
Message-ID: <C9B5F12337F6F841B35C404CF0554ACB5FE71942@SZXEMA509-MBS.china.huawei.com>
References: <C9B5F12337F6F841B35C404CF0554ACB5FE6A1CF@SZXEMA509-MBS.china.huawei.com> <000401cf1be4$302cf5a0$9086e0e0$@cernet.edu.cn> <C9B5F12337F6F841B35C404CF0554ACB5FE7005F@SZXEMA509-MBS.china.huawei.com> <53011B28.1070808@gmail.com> <C9B5F12337F6F841B35C404CF0554ACB5FE7149F@SZXEMA509-MBS.china.huawei.com> <530260F0.5090606@gmail.com>
In-Reply-To: <530260F0.5090606@gmail.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: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-CFilter-Loop: Reflected
Archived-At: http://mailarchive.ietf.org/arch/msg/openv6/IicTURnBuQ1kLyW7qIjRRxe7rEM
Cc: Jun Bi <junbi@tsinghua.edu.cn>, "Diego R. Lopez" <diego@tid.es>, "openv6@ietf.org" <openv6@ietf.org>
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: Tue, 18 Feb 2014 08:52:20 -0000

Thanks a lot. I've updated the doodle (http://doodle.com/pb3n9abm7w2gbdsp ). Two more options are now available: Tuesday 1420-1550 and Wednesday 1300-1500.

Regards,
Shucheng (Will)


> -----Original Message-----
> From: Openv6 [mailto:openv6-bounces@ietf.org] On Behalf Of Brian E
> Carpenter
> Sent: Tuesday, February 18, 2014 3:20 AM
> To: Liushucheng (Will)
> Cc: openv6@ietf.org
> Subject: Re: [Openv6] Openv6 Bar BoF sheduling
> 
> For example, there are no IPv6 sessions at the following times:
> 
> Tuesday 1420-1550
> Wednesday 1300-1500
> Thursday 1520-1650
> 
> Regards
>    Brian
> 
> On 17/02/2014 19:38, Liushucheng (Will) wrote:
> > Hi Brian,
> >
> > Thanks for your response. I've received some other similar feedbacks. It
> seems that these options are not enough. Would you please suggest some
> other slots? Thanks.
> >
> > Regards,
> > Shucheng (Will)
> >
> >
> >> -----Original Message-----
> >> From: Brian E Carpenter [mailto:brian.e.carpenter@gmail.com]
> >> Sent: Monday, February 17, 2014 4:10 AM
> >> To: Liushucheng (Will)
> >> Cc: openv6@ietf.org
> >> Subject: Re: [Openv6] Openv6 Bar BoF sheduling
> >>
> >> Hi,
> >>
> >> The Doodle only proposes times that clash with the plenary sessions
> >> or with dinner time after them. Sorry, not possible for me.
> >>
> >> Regards
> >>    Brian
> >>
> >> On 13/02/2014 16:56, Liushucheng (Will) wrote:
> >>> 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
> >>> --------------------------------------------------------------------
> >>> --
> >>> -------------
> >>>
> >>>
> >>>
> >>>
> >>> --------------------------------------------------------------------
> >>> --
> >>> --
> >>>
> >>> _______________________________________________
> >>> Openv6 mailing list
> >>> Openv6@ietf.org
> >>> https://www.ietf.org/mailman/listinfo/openv6
> 
> _______________________________________________
> Openv6 mailing list
> Openv6@ietf.org
> https://www.ietf.org/mailman/listinfo/openv6