Re: [Idr] WG Adoption call fordraft-peng-idr-segment-routing-te-policy-attr-05 (9/26/2023-10/10/2023)

"易昕昕(联通集团本部)" <yixx3@chinaunicom.cn> Wed, 11 October 2023 09:30 UTC

Return-Path: <yixx3@chinaunicom.cn>
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 F0A16C151525 for <idr@ietfa.amsl.com>; Wed, 11 Oct 2023 02:30:38 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.328
X-Spam-Level:
X-Spam-Status: No, score=-1.328 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, INVALID_MSGID=0.568, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, T_KAM_HTML_FONT_INVALID=0.01, T_SCC_BODY_TEXT_LINE=-0.01, URIBL_DBL_BLOCKED_OPENDNS=0.001, URIBL_ZEN_BLOCKED_OPENDNS=0.001] autolearn=no 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 eS-W_mRfsYLc for <idr@ietfa.amsl.com>; Wed, 11 Oct 2023 02:30:36 -0700 (PDT)
Received: from senda.mailex.chinaunicom.cn (senda.mailex.chinaunicom.cn [123.138.59.136]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id D1502C1519BB for <idr@ietf.org>; Wed, 11 Oct 2023 02:30:13 -0700 (PDT)
Received: from M10-XA-MLCEN03.MailSrv.cnc.intra (unknown [10.236.3.199]) by senda.mailex.chinaunicom.cn (SkyGuard) with ESMTPS id 4S56x73GL3z6Rb9f for <idr@ietf.org>; Wed, 11 Oct 2023 17:32:11 +0800 (CST)
Received: from smtpbg.qq.com (10.237.2.97) by M10-XA-MLCEN03.MailSrv.cnc.intra (10.236.3.199) with Microsoft SMTP Server id 15.0.1497.48; Wed, 11 Oct 2023 17:30:03 +0800
X-QQ-mid: Ymail-xx24b003-t1697016601thr
Received: from yixx-PC (unknown [10.2.109.38]) by smtp.qq.com (ESMTP) with id ; Wed, 11 Oct 2023 17:30:01 +0800 (CST)
X-QQ-SSF: 01900000000000G0ZF10000A0000000
X-QQ-GoodBg: 0
From: "易昕昕(联通集团本部)" <yixx3@chinaunicom.cn>
To: shares <shares@ndzh.com>, idr <idr@ietf.org>
Date: Wed, 11 Oct 2023 17:30:02 +0800
References: <BYAPR08MB487268B41AB9991CDA09CAC0B3C2A@BYAPR08MB4872.namprd08.prod.outlook.com>
X-Priority: 3
X-Has-Attach: no
X-Mailer: Foxmail 7.2.23.119[cn]
MIME-Version: 1.0
Message-ID: <202310111730015827273@chinaunicom.cn>
Content-Type: multipart/alternative; boundary="----=_001_NextPart852466627573_=----"
X-QQ-SENDSIZE: 520
Feedback-ID: Ymail-xx:chinaunicom.cn:mail-xx:mail-xx24b003-zhyw45w
Archived-At: <https://mailarchive.ietf.org/arch/msg/idr/hutiDXGpWTZUWjiQiquOmbPnwO0>
Subject: Re: [Idr] WG Adoption call fordraft-peng-idr-segment-routing-te-policy-attr-05 (9/26/2023-10/10/2023)
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: Wed, 11 Oct 2023 09:30:39 -0000

Hi Sue,
      I have reviewed this draft and I support the adoption.
     And I see no issue with the alignment.

Thanks!

Xinxin Yi
China Unicom

________________________________

发件人: Susan Hares<mailto:shares@ndzh.com>
发送时间: 2023-09-27 10:32
收件人: idr@ietf.org<mailto:idr@ietf.org>
主题: [警惕!外部邮件][Idr]WG Adoption call fordraft-peng-idr-segment-routing-te-policy-attr-05 (9/26/2023-10/10/2023)
This begins a 2-week WG adoption call for
draft-peng-idr-segment-routing-te-policy-attr-05
(https://datatracker.ietf.org/doc/draft-peng-idr-segment-routing-te-policy-attr/)

In your comments, please indicate
“support” or “no support”.

Please also consider the following questions:

1) Are these new segment types are useful for networks
Using alternate algorithms?

2) This draft will need to align with the
draft-ietf-idr-segment-routing-te-policy
split into  draft-ietf-idr-segment-routing-te-policy
and draft-ietf-idr-sr-segtypes-ext-01.

Do you see any issues with this alignment?

Cheerily, Sue Hares


如果您错误接收了该邮件,请通过电子邮件立即通知我们。请回复邮件到 hqs-spmc@chinaunicom.cn,即可以退订此邮件。我们将立即将您的信息从我们的发送目录中删除。 If you have received this email in error please notify us immediately by e-mail. Please reply to hqs-spmc@chinaunicom.cn ,you can unsubscribe from this mail. We will immediately remove your information from send catalogue of our.