[spring] 答复: IPv6+??

Lizhenbin <lizhenbin@huawei.com> Sat, 04 July 2020 08:08 UTC

Return-Path: <lizhenbin@huawei.com>
X-Original-To: spring@ietfa.amsl.com
Delivered-To: spring@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 552283A0D13 for <spring@ietfa.amsl.com>; Sat, 4 Jul 2020 01:08:18 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level:
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_MSPIKE_H2=-0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
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 oJEffsUQ3Lmi for <spring@ietfa.amsl.com>; Sat, 4 Jul 2020 01:08:16 -0700 (PDT)
Received: from huawei.com (lhrrgout.huawei.com [185.176.76.210]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 8F6143A0D12 for <spring@ietf.org>; Sat, 4 Jul 2020 01:08:16 -0700 (PDT)
Received: from lhreml710-chm.china.huawei.com (unknown [172.18.7.108]) by Forcepoint Email with ESMTP id 4C1CA28D87229DC202FE for <spring@ietf.org>; Sat, 4 Jul 2020 09:08:12 +0100 (IST)
Received: from lhreml710-chm.china.huawei.com (10.201.108.61) by lhreml710-chm.china.huawei.com (10.201.108.61) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256) id 15.1.1913.5; Sat, 4 Jul 2020 09:08:12 +0100
Received: from DGGEMM406-HUB.china.huawei.com (10.3.20.214) by lhreml710-chm.china.huawei.com (10.201.108.61) with Microsoft SMTP Server (version=TLS1_0, cipher=TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA) id 15.1.1913.5 via Frontend Transport; Sat, 4 Jul 2020 09:08:11 +0100
Received: from DGGEMM512-MBS.china.huawei.com ([169.254.4.204]) by DGGEMM406-HUB.china.huawei.com ([10.3.20.214]) with mapi id 14.03.0487.000; Sat, 4 Jul 2020 16:08:05 +0800
From: Lizhenbin <lizhenbin@huawei.com>
To: Andrew Alston <Andrew.Alston@liquidtelecom.com>, "spring@ietf.org" <spring@ietf.org>
Thread-Topic: IPv6+??
Thread-Index: AQHWUV/XdivlUhERMkWwlNxvQxGzYqj3D6aj
Date: Sat, 4 Jul 2020 08:08:05 +0000
Message-ID: <5A5B4DE12C0DAC44AF501CD9A2B01A8D937AB113@dggemm512-mbs.china.huawei.com>
References: <E23B5DB3-F364-43CA-817E-DC6099B555AF@liquidtelecom.com>
In-Reply-To: <E23B5DB3-F364-43CA-817E-DC6099B555AF@liquidtelecom.com>
Accept-Language: zh-CN, en-US
Content-Language: zh-CN
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [10.45.169.132]
Content-Type: multipart/alternative; boundary="_000_5A5B4DE12C0DAC44AF501CD9A2B01A8D937AB113dggemm512mbschi_"
MIME-Version: 1.0
X-CFilter-Loop: Reflected
Archived-At: <https://mailarchive.ietf.org/arch/msg/spring/oQhUrwywSvf7eV-LO890VUDTgUw>
Subject: [spring] =?gb2312?b?tPC4tDogSVB2Nis/Pw==?=
X-BeenThere: spring@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "Source Packet Routing in NetworkinG \(SPRING\)" <spring.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/spring>, <mailto:spring-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/spring/>
List-Post: <mailto:spring@ietf.org>
List-Help: <mailto:spring-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/spring>, <mailto:spring-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 04 Jul 2020 08:08:18 -0000

Hi Andrew,

Thanks for your paying attention to the website. Please refer to my clarification.



a. SRv6 is the technology based on IPv6. In the past 20+ years IPv6 has being deployed. One of the most important drives is the address space. The development of 5G and cloud proposes the new chances for the development and deployment of IPv6. Depending on the native IP reacheability and providing rich attributes based on the IPv6 extension headers, IPv6 can provide flexible connectivity to satisfy the requirements of 5G and cloud. SRv6 is the typical representative solutions. This makes this round of IPv6-based innovations and deployments shows the new characteristics of the times to some extent. Then IPv6+ concept is proposed.  It means the solutions is based on IPv6 and used for the scenarios of 5G and cloud.

b. IPv6+  has nothing with the New IP. It is apparent that the solutions proposed in the IPv6+ are based on the IPv6 and all the standardization work is being done in IETF and has nothing with ITU-T.



I am not sure if it is appropriate to discuss this work in the mailing list of SPRING WG.  More questions and comments can be sent to ipv6plus@outlook.com<mailto:ipv6plus@outlook.com>.





Best Regards,

Robin







________________________________
·¢¼þÈË: spring [spring-bounces@ietf.org] ´ú±í Andrew Alston [Andrew.Alston@liquidtelecom.com]
·¢ËÍʱ¼ä: 2020Äê7ÔÂ4ÈÕ 1:31
ÊÕ¼þÈË: spring@ietf.org
Ö÷Ìâ: [spring] IPv6+??

Hi All,

I came across this website: https://www.ipv6plus.net/

Now, I wish to clarify a few things.


  1.  This website seems to imply ¨C strong ¨C that Srv6 is not infact IPv6 ¨C but rather IPv6+ - is this the position of the member of this working group or is this simply someones bizarre idea?

[Robin

  1.  This site seems heavily related to the new ip stuff that was presented to the ITU ¨C does anyone here know if there is any actual relation between this and that crowd?

Thanks

Andrew