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

Lizhenbin <lizhenbin@huawei.com> Thu, 20 February 2020 16:53 UTC

Return-Path: <lizhenbin@huawei.com>
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 E86F4120957; Thu, 20 Feb 2020 08:53:41 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.2
X-Spam-Level:
X-Spam-Status: No, score=-4.2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, 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 bvMdbMzQ9ppU; Thu, 20 Feb 2020 08:53:39 -0800 (PST)
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 A4F36120954; Thu, 20 Feb 2020 08:53:39 -0800 (PST)
Received: from LHREML711-CAH.china.huawei.com (unknown [172.18.7.107]) by Forcepoint Email with ESMTP id 647B73D33284E467255C; Thu, 20 Feb 2020 16:53:37 +0000 (GMT)
Received: from lhreml729-chm.china.huawei.com (10.201.108.80) by LHREML711-CAH.china.huawei.com (10.201.108.34) with Microsoft SMTP Server (TLS) id 14.3.408.0; Thu, 20 Feb 2020 16:53:37 +0000
Received: from lhreml729-chm.china.huawei.com (10.201.108.80) by lhreml729-chm.china.huawei.com (10.201.108.80) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256) id 15.1.1713.5; Thu, 20 Feb 2020 16:53:36 +0000
Received: from DGGEMM424-HUB.china.huawei.com (10.1.198.41) by lhreml729-chm.china.huawei.com (10.201.108.80) with Microsoft SMTP Server (version=TLS1_0, cipher=TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA) id 15.1.1713.5 via Frontend Transport; Thu, 20 Feb 2020 16:53:36 +0000
Received: from DGGEMM532-MBX.china.huawei.com ([169.254.7.192]) by dggemm424-hub.china.huawei.com ([10.1.198.41]) with mapi id 14.03.0439.000; Fri, 21 Feb 2020 00:53:24 +0800
From: Lizhenbin <lizhenbin@huawei.com>
To: "spring@ietf.org" <spring@ietf.org>, "ipv6@ietf.org" <ipv6@ietf.org>
CC: Weiqiang Cheng <chengweiqiang@chinamobile.com>, Feng Zhao <zhaofeng@caict.ac.cn>, "Chengli (Cheng Li)" <chengli13@huawei.com>, Li Cong <licong.bri@chinatelecom.cn>, Chongfeng Xie <xiechf.bri@chinatelecom.cn>, Hui Tian <tianhui@caict.ac.cn>
Subject: FW: New Version Notification for draft-cl-spring-generalized-srv6-np-00.txt
Thread-Topic: New Version Notification for draft-cl-spring-generalized-srv6-np-00.txt
Thread-Index: AQHV4L8pPBvC1jQlwUyZhWB+7Pl6kqgkVtBH
Date: Thu, 20 Feb 2020 16:53:24 +0000
Message-ID: <5A5B4DE12C0DAC44AF501CD9A2B01A8D9363AD84@DGGEMM532-MBX.china.huawei.com>
References: <158141396093.20043.3935070177094525544.idtracker@ietfa.amsl.com>
In-Reply-To: <158141396093.20043.3935070177094525544.idtracker@ietfa.amsl.com>
Accept-Language: zh-CN, en-US
Content-Language: zh-CN
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [10.45.208.200]
Content-Type: text/plain; charset="gb2312"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-CFilter-Loop: Reflected
Archived-At: <https://mailarchive.ietf.org/arch/msg/ipv6/pGe8YHtWsiaZFXiSklcCeTNgLq8>
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: Thu, 20 Feb 2020 16:53:42 -0000

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