From cathy.zhou@huawei.com Fri Jan 17 17:49:47 2014 Return-Path: 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 B651D1AC4A3 for ; Fri, 17 Jan 2014 17:49:47 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -4.739 X-Spam-Level: X-Spam-Status: No, score=-4.739 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, RP_MATCHES_RCVD=-0.538, 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 cEbg0waBqDXl for ; Fri, 17 Jan 2014 17:49:46 -0800 (PST) Received: from lhrrgout.huawei.com (lhrrgout.huawei.com [194.213.3.17]) by ietfa.amsl.com (Postfix) with ESMTP id 96AB81A1F3F for ; Fri, 17 Jan 2014 17:49:46 -0800 (PST) Received: from 172.18.7.190 (EHLO lhreml203-edg.china.huawei.com) ([172.18.7.190]) by lhrrg02-dlp.huawei.com (MOS 4.3.7-GA FastPath queued) with ESMTP id BAB59908; Sat, 18 Jan 2014 01:49:33 +0000 (GMT) Received: from LHREML405-HUB.china.huawei.com (10.201.5.242) by lhreml203-edg.huawei.com (172.18.7.221) with Microsoft SMTP Server (TLS) id 14.3.158.1; Sat, 18 Jan 2014 01:48:32 +0000 Received: from SZXEMA408-HUB.china.huawei.com (10.82.72.40) by lhreml405-hub.china.huawei.com (10.201.5.242) with Microsoft SMTP Server (TLS) id 14.3.158.1; Sat, 18 Jan 2014 01:49:32 +0000 Received: from SZXEMA512-MBX.china.huawei.com ([169.254.7.155]) by SZXEMA408-HUB.china.huawei.com ([10.82.72.40]) with mapi id 14.03.0158.001; Sat, 18 Jan 2014 09:49:30 +0800 From: "Zhouqian (Cathy)" To: "openv6@ietf.org" Thread-Topic: test Thread-Index: Ac8T74Y2tgYwZlrLTLyweVhmQbRKtg== Date: Sat, 18 Jan 2014 01:49:29 +0000 Message-ID: Accept-Language: zh-CN, en-US Content-Language: zh-CN X-MS-Has-Attach: X-MS-TNEF-Correlator: x-originating-ip: [10.66.76.105] Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 X-CFilter-Loop: Reflected Subject: [Openv6] test X-BeenThere: openv6@ietf.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: Openv6 discussion list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 18 Jan 2014 01:49:47 -0000 Best Regards, Cathy From liushucheng@huawei.com Fri Jan 17 17:56:26 2014 Return-Path: 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 D8B0E1ACCDF for ; Fri, 17 Jan 2014 17:56:26 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -4.738 X-Spam-Level: X-Spam-Status: No, score=-4.738 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-2.3, RP_MATCHES_RCVD=-0.538, 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 DbBeLaZhncQ6 for ; Fri, 17 Jan 2014 17:56:25 -0800 (PST) Received: from lhrrgout.huawei.com (lhrrgout.huawei.com [194.213.3.17]) by ietfa.amsl.com (Postfix) with ESMTP id 60EC21AC4A3 for ; Fri, 17 Jan 2014 17:56:25 -0800 (PST) Received: from 172.18.7.190 (EHLO lhreml203-edg.china.huawei.com) ([172.18.7.190]) by lhrrg02-dlp.huawei.com (MOS 4.3.7-GA FastPath queued) with ESMTP id BAB60155; Sat, 18 Jan 2014 01:56:12 +0000 (GMT) Received: from LHREML401-HUB.china.huawei.com (10.201.5.240) by lhreml203-edg.huawei.com (172.18.7.221) with Microsoft SMTP Server (TLS) id 14.3.158.1; Sat, 18 Jan 2014 01:55:10 +0000 Received: from SZXEMA407-HUB.china.huawei.com (10.82.72.39) by lhreml401-hub.china.huawei.com (10.201.5.240) with Microsoft SMTP Server (TLS) id 14.3.158.1; Sat, 18 Jan 2014 01:56:11 +0000 Received: from SZXEMA509-MBS.china.huawei.com ([169.254.2.102]) by SZXEMA407-HUB.china.huawei.com ([10.82.72.39]) with mapi id 14.03.0158.001; Sat, 18 Jan 2014 09:56:07 +0800 From: "Liushucheng (Will)" To: "Openv6@ietf.org" Thread-Topic: test Thread-Index: Ac8T8HN4krXDlOv3SVGNpRKE/370sQ== Date: Sat, 18 Jan 2014 01:56:07 +0000 Message-ID: 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_C9B5F12337F6F841B35C404CF0554ACB5FE66D82SZXEMA509MBSchi_" MIME-Version: 1.0 X-CFilter-Loop: Reflected Subject: [Openv6] test X-BeenThere: openv6@ietf.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: Openv6 discussion list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 18 Jan 2014 01:56:27 -0000 --_000_C9B5F12337F6F841B35C404CF0554ACB5FE66D82SZXEMA509MBSchi_ Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable Regards, Shucheng LIU (Will) ---------------------------------------------------------------------------= -------- Shucheng LIU (Will), Ph.D. Researcher & Standard Representative Huawei Technologies Co.,Ltd liushucheng@huawei.com http://www.linkedin.com/in/shucheng ---------------------------------------------------------------------------= -------- --_000_C9B5F12337F6F841B35C404CF0554ACB5FE66D82SZXEMA509MBSchi_ Content-Type: text/html; charset="us-ascii" Content-Transfer-Encoding: quoted-printable

 

 

Regards,

Shucheng LIU (Will)<= /span>

----------------------------------------------------------------= -------------------

Shucheng LIU (Will), Ph.D.

Researcher & Standard Representative

Huawei Technologies Co.,Ltd

liushucheng@huawei.com

http://www.linkedin.com/in/shucheng=

----------------------------------------------------------------= -------------------

 

--_000_C9B5F12337F6F841B35C404CF0554ACB5FE66D82SZXEMA509MBSchi_-- From junbi@tsinghua.edu.cn Sat Jan 18 00:20:56 2014 Return-Path: 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 776AB1A1F78 for ; Sat, 18 Jan 2014 00:20:56 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -1.04 X-Spam-Level: X-Spam-Status: No, score=-1.04 tagged_above=-999 required=5 tests=[BAYES_05=-0.5, RP_MATCHES_RCVD=-0.538, SPF_HELO_PASS=-0.001, 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 Dcv9PGYuR8im for ; Sat, 18 Jan 2014 00:20:53 -0800 (PST) Received: from tsinghua.edu.cn (smtp06.tsinghua.edu.cn [166.111.204.35]) by ietfa.amsl.com (Postfix) with ESMTP id 226071AD7C0 for ; Sat, 18 Jan 2014 00:20:48 -0800 (PST) Received: from junbithinkpadx1 (unknown [59.66.53.172]) by app2 (Coremail) with SMTP id C8xvpgBn9PhPOdpS+AQTAA--.2739S2; Sat, 18 Jan 2014 16:20:31 +0800 (CST) From: "Jun Bi" To: References: In-Reply-To: Date: Sat, 18 Jan 2014 16:20:31 +0800 Message-ID: <006901cf1426$2729d740$757d85c0$@tsinghua.edu.cn> MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit X-Mailer: Microsoft Outlook 15.0 Thread-Index: AQIfsi2ge764x9gNDiotEBzJn4yszJno57zg Content-Language: zh-cn X-CM-TRANSID: C8xvpgBn9PhPOdpS+AQTAA--.2739S2 X-Coremail-Antispam: 1UD129KBjDUn29KB7ZKAUJUUUUU529EdanIXcx71UUUUU7v73 VFW2AGmfu7bjvjm3AaLaJ3UjIYCTnIWjp_UUU5T7k0a2IF6r1UM7kC6x804xWl14x267AK xVWUJVW8JwAFc2x0x2IEx4CE42xK8VAvwI8IcIk0rVWrJVCq3wAFIxvE14AKwVWUJVWUGw A2ocxC64kIII0Yj41l84ACjcxK6xIIjxv20xvE14v26F1j6w1UM28EF7xvwVC0I7IYx2IY 6xkF7I0E14v26F4j6r4UJwA2z4x0Y4vEx4A2jsIE14v26rxl6s0DM28EF7xvwVC2z280aV CY1x0267AKxVW0oVCq3wAS0I0E0xvYzxvE52x082IY62kv0487Mc02F40EFcxC0VAKzVAq x4xG6I80ewAv7VC0I7IYx2IY67AKxVWUXVWUAwAv7VC2z280aVAFwI0_Jr0_Gr1lOx8S6x CaFVCjc4AY6r1j6r4UM4x0Y48IcxkI7VAKI48JMxkIecxEwVAFwVW8ZwCF04k20xvY0x0E wIxGrwC20s026c02F40E14v26r1j6r18MI8I3I0E7480Y4vE14v26r106r1rMI8E67AF67 kF1VAFwI0_Jr0_JrylIxkGc2Ij64vIr41lIxAIcVC0I7IYx2IY67AKxVWUJVWUCwCI42IY 6xIIjxv20xvEc7CjxVAFwI0_Jr0_Gr1lIxAIcVCF04k26cxKx2IYs7xG6Fyj6rWUJwCI42 IY6I8E87Iv67AKxVWUJVW8JwCI42IY6I8E87Iv6xkF7I0E14v26r1j6r4UYxBIdaVFxhVj vjDU0xZFpf9x0piyv3UUUUUU= X-CM-SenderInfo: xmxquxo6wvx0pjkxthxhgxhubq/ Subject: Re: [Openv6] test X-BeenThere: openv6@ietf.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: Openv6 discussion list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 18 Jan 2014 08:20:56 -0000 Hello every one, This is Prof. Jun Bi from Tsinghua University. This is a test message . Jun -----Original Message----- From: Openv6 [mailto:openv6-bounces@ietf.org] On Behalf Of Zhouqian (Cathy) Sent: Saturday, January 18, 2014 9:49 AM To: openv6@ietf.org Subject: [Openv6] test Best Regards, Cathy _______________________________________________ Openv6 mailing list Openv6@ietf.org https://www.ietf.org/mailman/listinfo/openv6 From liushucheng@huawei.com Mon Jan 27 00:16:24 2014 Return-Path: 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 38AAA1A008A for ; Mon, 27 Jan 2014 00:16:24 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -4.735 X-Spam-Level: X-Spam-Status: No, score=-4.735 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-2.3, RP_MATCHES_RCVD=-0.535, 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 yf4FUHa_7NT9 for ; Mon, 27 Jan 2014 00:16:22 -0800 (PST) Received: from lhrrgout.huawei.com (lhrrgout.huawei.com [194.213.3.17]) by ietfa.amsl.com (Postfix) with ESMTP id 83DFE1A005C for ; Mon, 27 Jan 2014 00:16:21 -0800 (PST) Received: from 172.18.7.190 (EHLO lhreml203-edg.china.huawei.com) ([172.18.7.190]) by lhrrg01-dlp.huawei.com (MOS 4.3.7-GA FastPath queued) with ESMTP id BCY54470; Mon, 27 Jan 2014 08:16:19 +0000 (GMT) Received: from LHREML405-HUB.china.huawei.com (10.201.5.242) by lhreml203-edg.huawei.com (172.18.7.221) with Microsoft SMTP Server (TLS) id 14.3.158.1; Mon, 27 Jan 2014 08:15:47 +0000 Received: from SZXEMA405-HUB.china.huawei.com (10.82.72.37) by lhreml405-hub.china.huawei.com (10.201.5.242) with Microsoft SMTP Server (TLS) id 14.3.158.1; Mon, 27 Jan 2014 08:16:13 +0000 Received: from SZXEMA509-MBS.china.huawei.com ([169.254.2.102]) by SZXEMA405-HUB.china.huawei.com ([10.82.72.37]) with mapi id 14.03.0158.001; Mon, 27 Jan 2014 16:16:06 +0800 From: "Liushucheng (Will)" To: "openv6@ietf.org" Thread-Topic: Starting discussion Thread-Index: Ac8bNi7o67iiH56VStS5Hxs2IMZUUgAAWUxA Date: Mon, 27 Jan 2014 08:16:05 +0000 Message-ID: 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_C9B5F12337F6F841B35C404CF0554ACB5FE6A1CFSZXEMA509MBSchi_" MIME-Version: 1.0 X-CFilter-Loop: Reflected Subject: [Openv6] Starting discussion X-BeenThere: openv6@ietf.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: Openv6 discussion list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 27 Jan 2014 08:16:24 -0000 --_000_C9B5F12337F6F841B35C404CF0554ACB5FE6A1CFSZXEMA509MBSchi_ Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable (Sorry for duplicated mails.) Hello, Thanks for joining the Open IPv6 (openv6) mailing list. It's great to see s= o 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 applicatio= ns, 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 incorpo= rate the transition policies, simplifying the different stages through the = transition and guaranteeing that current decisions do not imply a complicat= ed 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 th= is open interface? In addition to the above questions, we've laid out an initial description o= f the problem in https://datatracker.ietf.org/doc/draft-sun-openv6-problem-= statement/ and are looking for productive discussion and feedback on this l= ist. 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 http://www.linkedin.com/in/shucheng ---------------------------------------------------------------------------= -------- --_000_C9B5F12337F6F841B35C404CF0554ACB5FE6A1CFSZXEMA509MBSchi_ Content-Type: text/html; charset="us-ascii" Content-Transfer-Encoding: quoted-printable

(Sorry = for duplicated mails.)

&n= bsp;

Hello,

 

Thanks for joining the Open IPv= 6 (openv6) mailing list. It’s great to see so much interest in the to= pic!

 

The following questions are lis= ted to be discussed here:
(1) What are the problems and use cases existing in various IPv6 applicatio= ns, 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 incorpo= rate the transition policies, simplifying the different stages through the = transition and guaranteeing that current decisions do not imply a complicat= ed 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 th= is open interface?

 

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

 

Regards,

Shucheng LIU (Will)<= /span>

----------------------------------------------------------------= -------------------

Shucheng LIU (Will), Ph.D.

Researcher & Standard Representative

Huawei Technologies Co.,Ltd

liushucheng@huawei.com=

http://www.linke= din.com/in/shucheng

----------------------------------------------------------------= -------------------

 

--_000_C9B5F12337F6F841B35C404CF0554ACB5FE6A1CFSZXEMA509MBSchi_-- From yaoguang@cernet.edu.cn Mon Jan 27 20:48:46 2014 Return-Path: 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 CFC251A0198 for ; Mon, 27 Jan 2014 20:48:46 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.434 X-Spam-Level: X-Spam-Status: No, score=-2.434 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RP_MATCHES_RCVD=-0.535] 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 nTqgmtWZqNiY for ; Mon, 27 Jan 2014 20:48:42 -0800 (PST) Received: from cernet.edu.cn (cernet.edu.cn [202.112.39.2]) by ietfa.amsl.com (Postfix) with ESMTP id CA2251A016B for ; Mon, 27 Jan 2014 20:48:41 -0800 (PST) Received: from AndrewYaoPC (unknown [59.66.253.132]) by centos (Coremail) with SMTP id AQAAf3CLMgMhM+dSvsgKAA--.796S2; Tue, 28 Jan 2014 12:33:37 +0800 (CST) From: "Guang Yao" To: "'Liushucheng \(Will\)'" , References: In-Reply-To: Date: Tue, 28 Jan 2014 12:48:29 +0800 Message-ID: <000401cf1be4$302cf5a0$9086e0e0$@cernet.edu.cn> MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_NextPart_000_0005_01CF1C27.3E51BC40" X-Mailer: Microsoft Outlook 15.0 Thread-Index: AQFvW9gPnTcDP4CyGvej6nmQe2mzJptZEKEg Content-Language: zh-cn X-CM-TRANSID: AQAAf3CLMgMhM+dSvsgKAA--.796S2 X-Coremail-Antispam: 1UD129KBjvJXoWxXrWfWr15KFWrJr18KFW3Wrg_yoWrJFyUpF W3Gw47t3WkJr1xCr4kXw18uw45Wa97J3yUJFnxXr9Yyw4UAa4Ikrn5tw4rZFy5Xr97Xr12 qr1qqrs8CFnrZFJanT9S1TB71UUUUU7qnTZGkaVYY2UrUUUUjbIjqfuFe4nvWSU5nxnvy2 9KBjDU0xBIdaVrnRJUUUvjb7Iv0xC_Cr1lb4IE77IF4wAFF20E14v26r1j6r4UM7CY07I2 0VC2zVCF04k26cxKx2IYs7xG6rWj6s0DM7CIcVAFz4kK6r1j6r18M28lY4IEw2IIxxk0rw A2z4x0Y4vE2Ix0cI8IcVAFwI0_Jr0_JF4l84ACjcxK6xIIjxv20xvEc7CjxVAFwI0_Jr0_ Gr1l84ACjcxK6I8E87Iv67AKxVW0oVCq3wA2z4x0Y4vEx4A2jsIEc7CjxVAFwI0_GcCE3s 1le2I262IYc4CY6c8Ij28IcVAaY2xG8wAqx4xG67k08I80eVW5JVWrJwAqx4xG6c804VAF z4xC04v7Mc02F40Ew4AK048IF2xKxVWUJVW8JwAqx4xG6xAIxVCFxsxG0wAv7VC2z280aV AFwI0_Jr0_Gr1lOx8S6xCaFVCjc4AY6r1j6r4UM4x0Y48IcxkI7VAKI48JM4x0Y48IcxkI 7VAKI48G6xCjnVAKz4kxMxkIecxEwVAFwVW8XwCF04k20xvY0x0EwIxGrwC20s026c02F4 0E14v26r106r1rMI8I3I0E7480Y4vE14v26r106r1rMI8E67AF67kF1VAFwI0_Jrv_JF1l IxkGc2Ij64vIr41lIxAIcVC0I7IYx2IY67AKxVWUJVWUCwCI42IY6xIIjxv20xvEc7CjxV AFwI0_Jr0_Gr1lIxAIcVCF04k26cxKx2IYs7xG6rW3Jr0E3s1lIxAIcVC2z280aVAFwI0_ Jr0_Gr1lIxAIcVC2z280aVCY1x0267AKxVWUJVW8JbIYCTnIWIevJa73UjIFyTuYvjxUcJ 5rDUUUU X-CM-SenderInfo: 51drw3xdqjquphuqv3oohg3hdfq/ Subject: Re: [Openv6] Starting discussion X-BeenThere: openv6@ietf.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: Openv6 discussion list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 28 Jan 2014 04:48:47 -0000 This is a multipart message in MIME format. ------=_NextPart_000_0005_01CF1C27.3E51BC40 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Hi Will and folks, I want to introduce SAVI and discuss whether it can be adopted in the OpenV6 framework. SAVI(Source Address Validation Improvements, http://tools.ietf.org/wg/savi/) sets up bindings between IP address and binding anchor. It has following features: 1. There are at least 3 SAVI solutions for IPv6: SAVI-DHCP,SAVI-FCFS, SAVI-SEND. The solutions are designed based on the address assignment mechanism (DHCPv6, Stateless, SEND-CGA). If new address assignment mechanisms (or address usage guideline) are introduced, e.g., IKEv2, Mobile IPv6, Ipv4/IPv6 transition, corresponding SAVI solutions should be implemented. 2. In general, only one of the SAVI solutions should be enabled, depending on the deployment scenario. 3. Multiple SAVI solutions can coexist on the same device. For example, SAVI-DHCP and SAVI-FCFS may work together for the scenarios where both DHCP and stateless addresses are allowed. 4. SAVI solutions have the same data plane model (or abstraction): binding table. Binding table contains the valid associations between IP address and the corresponding binding anchor. 5. The differences of SAVI solutions are in the control plane. Difference SAVI solutions snoop difference protocols, and even data packets. 6. SAVI solutions can benefit from a global view of the network, because a protection perimeter composed by multiple SAVI devices can be automatically formed. We have implemented a prototype of Openflow-based SAVI. It is quite simple and effective, but it's a pity that it cannot work with non-Openflow devices. Besides, currently it is hard for the Openflow-based SAVI to cooperate with other applications, e.g., transition applications. We are interested in whether an Openv6-based SAVI can have more advantages than the Openflow-based one? (it seems more general interfaces are supported?) Best regards, Guang From: Liushucheng (Will) [mailto:liushucheng@huawei.com] Sent: Monday, January 27, 2014 4:16 PM To: 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 http://www.linkedin.com/in/shucheng ---------------------------------------------------------------------------- ------- ------=_NextPart_000_0005_01CF1C27.3E51BC40 Content-Type: text/html; charset="us-ascii" Content-Transfer-Encoding: quoted-printable

Hi Will and = folks,

 

I want = to introduce SAVI and discuss whether it can be adopted in the OpenV6 = framework.

 

SAVI(Source Address Validation = Improvements, http://tools.ietf.org/wg/savi/) sets up bindings = between IP address and binding anchor. It has following = features:

 

1.       = There are at least = 3 SAVI solutions for IPv6: SAVI-DHCP,SAVI-FCFS, SAVI-SEND. The solutions = are designed based on the address assignment mechanism (DHCPv6, = Stateless, SEND-CGA). If new address assignment mechanisms (or address = usage guideline) are introduced, e.g., IKEv2, Mobile IPv6, Ipv4/IPv6 = transition, corresponding SAVI solutions should be = implemented.

 

2.       = In general, only = one of the SAVI solutions should be enabled, depending on the deployment = scenario.

 

3.       = Multiple SAVI = solutions can coexist on the same device. For example, SAVI-DHCP and = SAVI-FCFS may work together for the scenarios where both DHCP and = stateless addresses are allowed.

 

4.       = SAVI solutions = have the same data plane model (or abstraction): binding table. Binding = table contains the valid associations between IP address and the = corresponding binding anchor.

 

5.       = The differences of = SAVI solutions are in the control plane. Difference SAVI solutions snoop = difference protocols, and even data packets.

 

6.       = SAVI solutions can = benefit from a global view of the network, because a protection = perimeter composed by multiple SAVI devices can be automatically = formed.

 

We have = implemented a prototype of Openflow-based SAVI. It is quite simple and = effective, but it’s a pity that it cannot work with non-Openflow = devices. Besides, currently it is hard for the Openflow-based SAVI to = cooperate with other applications, e.g., transition applications. We are = interested in whether an Openv6-based SAVI can have more advantages than = the Openflow-based one? (it seems more general interfaces are = supported?)

 

Best = regards,

Guang

 

 

From: Liushucheng (Will) = [mailto:liushucheng@huawei.com]
Sent: Monday, January 27, = 2014 4:16 PM
To: 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. J

 

Regards,

Shucheng = LIU (Will)

-----------------------------------------------= ------------------------------------

Shucheng LIU (Will), = Ph.D.

Researcher & Standard Representative =

Huawei Technologies Co.,Ltd

liushucheng@huawei.com

http://www.linkedin.com/in/s= hucheng

-----------------------------------------------= ------------------------------------

 

------=_NextPart_000_0005_01CF1C27.3E51BC40--