转发: FW: New Version Notification for draft-cl-spring-generalized-srv6-np-00.txt

"licong@chinatelecom.cn" <licong@chinatelecom.cn> Sun, 23 February 2020 13:20 UTC

Return-Path: <licong@chinatelecom.cn>
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 78B2E3A0EF9; Sun, 23 Feb 2020 05:20:17 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.889
X-Spam-Level:
X-Spam-Status: No, score=-1.889 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, SPF_PASS=-0.001, T_KAM_HTML_FONT_INVALID=0.01, 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 durrEIOi1hnF; Sun, 23 Feb 2020 05:20:14 -0800 (PST)
Received: from chinatelecom.cn (prt-mail.chinatelecom.cn [42.123.76.228]) by ietfa.amsl.com (Postfix) with ESMTP id AFFFB3A0EF6; Sun, 23 Feb 2020 05:20:01 -0800 (PST)
HMM_SOURCE_IP: 172.18.0.92:55825.246777062
HMM_ATTACHE_NUM: 0000
HMM_SOURCE_TYPE: SMTP
Received: from clientip-111.199.186.70?logid-8680B5D6829A43059E3D61458F328431 (unknown [172.18.0.92]) by chinatelecom.cn (HERMES) with SMTP id 29193280098; Sun, 23 Feb 2020 21:19:50 +0800 (CST)
X-189-SAVE-TO-SEND: 71080549@chinatelecom.cn
Received: from ([172.18.0.92]) by App0021 with ESMTP id 8680B5D6829A43059E3D61458F328431 for spring@ietf.org; Sun Feb 23 21:19:53 2020
X-Transaction-ID: 8680B5D6829A43059E3D61458F328431
X-filter-score: filter<0>
X-Real-From: licong@chinatelecom.cn
X-Receive-IP: 172.18.0.92
X-MEDUSA-Status: 0
Date: Sun, 23 Feb 2020 21:19:49 +0800
From: "licong@chinatelecom.cn" <licong@chinatelecom.cn>
To: spring <spring@ietf.org>, ipv6 <ipv6@ietf.org>
Subject: 转发: FW: New Version Notification for draft-cl-spring-generalized-srv6-np-00.txt
X-Priority: 3
X-Has-Attach: no
X-Mailer: Foxmail 7.2.10.151[cn]
Mime-Version: 1.0
Message-ID: <2020022321194810805031@chinatelecom.cn>
Content-Type: multipart/alternative; boundary="----=_001_NextPart438378370152_=----"
Archived-At: <https://mailarchive.ietf.org/arch/msg/ipv6/g9RFPPMX-WVfwA2MPRUp40wuPYM>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.29
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: Sun, 23 Feb 2020 13:20:18 -0000

Hi Group,

From carriers' point view, the application scenario for the Generalize SRv6 SID is valid. It can provide some important functions as follows.
1.  In the process of network evolution, there are cases where IPv6 networks and IPv4 networks coexist. An SRv6 packet may cross IPv4 networking. Usually, the packet will be transported by an IPv6 over IPv4 tunnel.G-SID provides two options for carrying IPv4 tunnel information.
2. In the SD-WAN scenario,  An SRv6 packet may cross the MPLS domain. The Generalized Segment Routing Header can effectively reduce the configuration in the middle nodes.

Best Regards,
Cong Li


李聪/Li Cong
新兴信息技术研究所 IP与未来网络研究中心
中国电信股份有限公司战略与创新研究院
地址:北京市昌平区北七家镇未来科技城南区中国电信北京信息科技创新园902室
邮编:102209
邮箱:licong@chinatelecom.cn
电话:(010)50902556
手机:18101266382
 
发件人: Lizhenbin
发送时间: 2020-02-21 00:53
收件人: spring@ietf.org; ipv6@ietf.org
抄送: Hui Tian; Chongfeng Xie; Li Cong; Feng Zhao
主题: FW: New Version Notification for draft-cl-spring-generalized-srv6-np-00.txt
Hi Folks,
We proposed following two drafts. They are to propose the unified mechanism based on Generalize SRv6 SID 
which can encapsulate Compressed SRv6 SID, MPLS Label and IPv4 tunnel information to cope with the 
emerging new requirements of SRv6 including SRv6 compression, crossing SR-MPLS domains and crossing 
IPv4 domains. At the same time the mechanisms keep the compatibility of the existing SRv6 Network Program 
mechanisms and comply with the basic rule of Segment Routing that the path is programmed in the ingress node 
without introducing extra network states in the transit nodes.
https://www.ietf.org/internet-drafts/draft-cl-spring-generalized-srv6-np-00.txt
https://www.ietf.org/internet-drafts/draft-lc-6man-generalized-srh-00.txt
 
 
Your comments are welcome.
 
 
 
Best Regards,
Zhenbin (Robin)
 
 
 
 
________________________________________
发件人: internet-drafts@ietf.org [internet-drafts@ietf.org]
发送时间: 2020年2月11日 17:39
收件人: Lizhenbin; Weiqiang Cheng; Feng Zhao; Chengli (Cheng Li); Li Cong; Chongfeng Xie; Hui Tian; Cong Li
主题: New Version Notification for draft-cl-spring-generalized-srv6-np-00.txt
 
A new version of I-D, draft-cl-spring-generalized-srv6-np-00.txt
has been successfully submitted by Zhenbin Li and posted to the
IETF repository.
 
Name:           draft-cl-spring-generalized-srv6-np
Revision:       00
Title:          Generalized SRv6 Network Programming
Document date:  2020-02-11
Group:          Individual Submission
Pages:          30
URL:            https://www.ietf.org/internet-drafts/draft-cl-spring-generalized-srv6-np-00.txt
Status:         https://datatracker.ietf.org/doc/draft-cl-spring-generalized-srv6-np/
Htmlized:       https://tools.ietf.org/html/draft-cl-spring-generalized-srv6-np-00
Htmlized:       https://datatracker.ietf.org/doc/html/draft-cl-spring-generalized-srv6-np
 
 
Abstract:
   As the deployment of SRv6, some new requirements are proposed, such
   as SRv6 compression, transporting over SR-MPLS/MPLS and IPv4 domains.
   Therefore, it is necessary to consider other types of segments or
   sub-paths in the end-to-end SRv6 network programming.
 
   This document proposes Generalized Segment Routing over IPv6 (G-SRv6)
   Networking Programming, which supports to encode multiple types of
   Segments in a SRH, called Generalized SRH (G-SRH).  These Segments
   can be called Generalized Segment, and the ID can be Generalized
   Segment Identifier (G-SID), which may include an SRv6 SID(128 bits),
   C-SIDs, MPLS labels, or IPv4 tunnel information.
 
   This document also defines the mechanisms of Generalized SRv6
   Networking Programming and the requirements of related protocol
   extensions of control plane and data plane.
 
 
 
 
Please note that it may take a couple of minutes from the time of submission
until the htmlized version and diff are available at tools.ietf.org.
 
The IETF Secretariat
--------------------------------------------------------------------
IETF IPv6 working group mailing list
ipv6@ietf.org
Administrative Requests: https://www.ietf.org/mailman/listinfo/ipv6
--------------------------------------------------------------------