[Idr] FW: New Version Notification for draft-lin-idr-sr-policy-seglist-id-02.txt

"Mengxiao.Chen" <chen.mengxiao@h3c.com> Thu, 09 March 2023 10:01 UTC

Return-Path: <chen.mengxiao@h3c.com>
X-Original-To: idr@ietfa.amsl.com
Delivered-To: idr@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 1E074C15C524; Thu, 9 Mar 2023 02:01:22 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.897
X-Spam-Level:
X-Spam-Status: No, score=-1.897 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_DBL_BLOCKED_OPENDNS=0.001, URIBL_ZEN_BLOCKED_OPENDNS=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 5e_qaRUxZqjn; Thu, 9 Mar 2023 02:01:18 -0800 (PST)
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 4D89AC14068D; Thu, 9 Mar 2023 02:01:11 -0800 (PST)
Received: from mail.maildlp.com ([172.25.15.154]) by h3cspam02-ex.h3c.com with ESMTP id 3299wnFa088017; Thu, 9 Mar 2023 17:58:49 +0800 (GMT-8) (envelope-from chen.mengxiao@h3c.com)
Received: from DAG2EX03-BASE.srv.huawei-3com.com (unknown [10.69.0.51]) by mail.maildlp.com (Postfix) with ESMTP id E633522B5A26; Thu, 9 Mar 2023 18:02:15 +0800 (CST)
Received: from DAG2EX09-IDC.srv.huawei-3com.com (172.20.54.132) by DAG2EX03-BASE.srv.huawei-3com.com (10.69.0.51) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256) id 15.1.2375.17; Thu, 9 Mar 2023 17:58:51 +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; Thu, 9 Mar 2023 17:58:51 +0800
From: "Mengxiao.Chen" <chen.mengxiao@h3c.com>
To: "idr@ietf.org" <idr@ietf.org>, spring <spring@ietf.org>
CC: linchangwang <linchangwang.04414@h3c.com>, "jiangwenying@chinamobile.com" <jiangwenying@chinamobile.com>, Weiqiang Cheng <chengweiqiang@chinamobile.com>
Thread-Topic: New Version Notification for draft-lin-idr-sr-policy-seglist-id-02.txt
Thread-Index: AQHZUmnC1waH7Z0zxkyLfY0j1TlfdK7yMLmA
Date: Thu, 09 Mar 2023 09:58:50 +0000
Message-ID: <3d766f2be00649da9208879cb5dd4e00@h3c.com>
References: <167835418543.59045.4546334833417123987@ietfa.amsl.com>
In-Reply-To: <167835418543.59045.4546334833417123987@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.152.251]
x-sender-location: DAG2
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-DNSRBL:
X-SPAM-SOURCE-CHECK: pass
X-MAIL: h3cspam02-ex.h3c.com 3299wnFa088017
Archived-At: <https://mailarchive.ietf.org/arch/msg/idr/BVMIhMQHLXg4q9LUFqhofhmZRb8>
Subject: [Idr] FW: New Version Notification for draft-lin-idr-sr-policy-seglist-id-02.txt
X-BeenThere: idr@ietf.org
X-Mailman-Version: 2.1.39
Precedence: list
List-Id: Inter-Domain Routing <idr.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/idr>, <mailto:idr-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/idr/>
List-Post: <mailto:idr@ietf.org>
List-Help: <mailto:idr-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/idr>, <mailto:idr-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 09 Mar 2023 10:01:22 -0000

Hi,

We have posted a new version of https://datatracker.ietf.org/doc/draft-lin-idr-sr-policy-seglist-id/ .

In Section 2, we cited the segment list identifier in PCEP and YANG, and explained the reason for defining two Sub-TLVs in Section 2.1 and 2.2:
" When signaling SR Policy by PCEP [I-D.ietf-pce-multipath], a segment list is identified by "Path ID", which is a 4-octet identifier.
  In the YANG data model for SR Policy [I-D.ietf-spring-sr-policy-yang], a segment-list is keyed by its name, which is a string.
  In this document, both the two forms of segment list identifier are provided to achieve greater flexibility. "

We are looking forward to receiving more comments and suggestions.

Thanks,
Mengxiao

-----Original Message-----
From: internet-drafts@ietf.org <internet-drafts@ietf.org>
Sent: Thursday, March 9, 2023 5:30 PM
To: linchangwang (RD) <linchangwang.04414@h3c.com>; Jiang Wenying <jiangwenying@chinamobile.com>; chenmengxiao (RD) <chen.mengxiao@h3c.com>; Weiqiang Cheng <chengweiqiang@chinamobile.com>; Wenying Jiang <jiangwenying@chinamobile.com>
Subject: New Version Notification for draft-lin-idr-sr-policy-seglist-id-02.txt


A new version of I-D, draft-lin-idr-sr-policy-seglist-id-02.txt
has been successfully submitted by Mengxiao Chen and posted to the
IETF repository.

Name:draft-lin-idr-sr-policy-seglist-id
Revision:02
Title:BGP SR Policy Extensions for Segment List Identifier
Document date:2023-03-09
Group:Individual Submission
Pages:8
URL:            https://www.ietf.org/archive/id/draft-lin-idr-sr-policy-seglist-id-02.txt
Status:         https://datatracker.ietf.org/doc/draft-lin-idr-sr-policy-seglist-id/
Htmlized:       https://datatracker.ietf.org/doc/html/draft-lin-idr-sr-policy-seglist-id
Diff:           https://author-tools.ietf.org/iddiff?url2=draft-lin-idr-sr-policy-seglist-id-02

Abstract:
   Segment Routing is a source routing paradigm that explicitly
   indicates the forwarding path for packets at the ingress node. An SR
   Policy is a set of candidate paths, each consisting of one or more
   segment lists. This document defines extensions to BGP SR Policy to
   specify the identifier of segment list.




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!