[spring] FW: New Version Notification for draft-lin-idr-sr-policy-headend-behavior-00.txt

Chenmengxiao <chen.mengxiao@h3c.com> Mon, 20 June 2022 01:16 UTC

Return-Path: <chen.mengxiao@h3c.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 32079C147921; Sun, 19 Jun 2022 18:16:45 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.907
X-Spam-Level:
X-Spam-Status: No, score=-1.907 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_BLOCKED=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([50.223.129.194]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id C6cVKhG7_oZA; Sun, 19 Jun 2022 18:16:40 -0700 (PDT)
Received: from h3cspam02-ex.h3c.com (smtp.h3c.com [60.191.123.50]) (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 7CBAFC14F73B; Sun, 19 Jun 2022 18:16:38 -0700 (PDT)
Received: from mail.maildlp.com ([172.25.15.154]) by h3cspam02-ex.h3c.com with ESMTP id 25K1DWPA015160; Mon, 20 Jun 2022 09:13:32 +0800 (GMT-8) (envelope-from chen.mengxiao@h3c.com)
Received: from DAG2EX03-BASE.srv.huawei-3com.com (unknown [10.8.0.66]) by mail.maildlp.com (Postfix) with ESMTP id 55B45229294A; Mon, 20 Jun 2022 09:16:51 +0800 (CST)
Received: from DAG2EX09-IDC.srv.huawei-3com.com (172.20.54.132) by DAG2EX03-BASE.srv.huawei-3com.com (10.8.0.66) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256) id 15.1.2375.17; Mon, 20 Jun 2022 09:13:32 +0800
Received: from DAG2EX09-IDC.srv.huawei-3com.com ([fe80::c83b:8401:2e7d:cb1b]) by DAG2EX09-IDC.srv.huawei-3com.com ([fe80::c83b:8401:2e7d:cb1b%6]) with mapi id 15.01.2375.017; Mon, 20 Jun 2022 09:13:32 +0800
From: Chenmengxiao <chen.mengxiao@h3c.com>
To: "idr@ietf.org" <idr@ietf.org>, "spring@ietf.org" <spring@ietf.org>
CC: linchangwang <linchangwang.04414@h3c.com>, "jiangwenying@chinamobile.com" <jiangwenying@chinamobile.com>, "liuyisong@chinamobile.com" <liuyisong@chinamobile.com>, Lihao <lihao@h3c.com>
Thread-Topic: New Version Notification for draft-lin-idr-sr-policy-headend-behavior-00.txt
Thread-Index: AQHYfJmA03QqqsJze0G9QCssubNcoK1TKc+Q
Date: Mon, 20 Jun 2022 01:13:31 +0000
Message-ID: <fec9fe1b004e40bc8e1f06988dc10cdf@h3c.com>
References: <165484514848.56173.9725592656242469622@ietfa.amsl.com>
In-Reply-To: <165484514848.56173.9725592656242469622@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.99.153.65]
x-sender-location: DAG2
Content-Type: multipart/alternative; boundary="_000_fec9fe1b004e40bc8e1f06988dc10cdfh3ccom_"
MIME-Version: 1.0
X-DNSRBL:
X-MAIL: h3cspam02-ex.h3c.com 25K1DWPA015160
Archived-At: <https://mailarchive.ietf.org/arch/msg/spring/g6mh_WZAgiS7VMWwueIyFeZyIr8>
Subject: [spring] FW: New Version Notification for draft-lin-idr-sr-policy-headend-behavior-00.txt
X-BeenThere: spring@ietf.org
X-Mailman-Version: 2.1.39
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: Mon, 20 Jun 2022 01:16:45 -0000

Hi idr & spring WG,



We posted a new draft: draft-lin-idr-sr-policy-headend-behavior-00. It's about carrying headend behavior when advertising SR Policy in BGP.



When a headend steers a packet into an SRv6 Policy, it may use specific behavior to encapsulate the segment list. RFC8986 defines 4 headend behaviors: H.Encaps, H.Encaps.Red, H.Encaps.L2, H.Encaps.L2.Red. Draft-filsfils-spring-srv6-net-pgm-insertion adds H.Insert and H.Insert.Red.



If the packet is steered by BSID, the headend will use corresponding behavior defined by BSID: End.B6.Encaps, End.B6.Encaps.Red, End.B6.Insert, End.B6.Insert.Red. However, if steered by other way, the network operator has to use additional tools, like NETCONF, to signal the headend behavior. So we hope the headend behavior can be specified along with the SR Policy distribution in BGP.



-----Original Message-----

From: internet-drafts@ietf.org [mailto:internet-drafts@ietf.org]

Sent: Friday, June 10, 2022 3:12 PM

To: linchangwang (RD) <linchangwang.04414@h3c.com>; lihao (02566, RD) <lihao@h3c.com>; Jiang Wenying <jiangwenying@chinamobile.com>; chenmengxiao (RD) <chen.mengxiao@h3c.com>; Wenying Jiang <jiangwenying@chinamobile.com>; Yisong Liu <liuyisong@chinamobile.com>

Subject: New Version Notification for draft-lin-idr-sr-policy-headend-behavior-00.txt





A new version of I-D, draft-lin-idr-sr-policy-headend-behavior-00.txt

has been successfully submitted by Mengxiao Chen and posted to the

IETF repository.



Name:               draft-lin-idr-sr-policy-headend-behavior

Revision:  00

Title:                  BGP Extensions of SR Policy for Headend Behavior

Document date:       2022-06-10

Group:               Individual Submission

Pages:               9

URL:            https://www.ietf.org/archive/id/draft-lin-idr-sr-policy-headend-behavior-00.txt

Status:         https://datatracker.ietf.org/doc/draft-lin-idr-sr-policy-headend-behavior/

Htmlized:       https://datatracker.ietf.org/doc/html/draft-lin-idr-sr-policy-headend-behavior





Abstract:

   This document defines extensions to Border Gateway Protocol (BGP) to

   distribute SR policies carrying headend behavior.









The IETF Secretariat





-------------------------------------------------------------------------------------------------------------------------------------
本邮件及其附件含有新华三集团的保密信息,仅限于发送给上面地址中列出
的个人或群组。禁止任何其他人以任何形式使用(包括但不限于全部或部分地泄露、复制、
或散发)本邮件中的信息。如果您错收了本邮件,请您立即电话或邮件通知发件人并删除本
邮件!
This e-mail and its attachments contain confidential information from New H3C, which is
intended only for the person or entity whose address is listed above. Any use of the
information contained herein in any way (including, but not limited to, total or partial
disclosure, reproduction, or dissemination) by persons other than the intended
recipient(s) is prohibited. If you receive this e-mail in error, please notify the sender
by phone or email immediately and delete it!