IETF Logo Mail Archive

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

linchangwang <linchangwang.04414@h3c.com> Mon, 09 October 2023 03:17 UTC

Return-Path: <linchangwang.04414@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 D39D3C151099 for <idr@ietfa.amsl.com>; Sun, 8 Oct 2023 20:17:01 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.905
X-Spam-Level:
X-Spam-Status: No, score=-6.905 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_HI=-5, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01, URIBL_BLOCKED=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 moYktiR3hlqH for <idr@ietfa.amsl.com>; Sun, 8 Oct 2023 20:16:57 -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 A6FD1C14F747 for <idr@ietf.org>; Sun, 8 Oct 2023 20:16:56 -0700 (PDT)
Received: from mail.maildlp.com ([172.25.15.154]) by h3cspam02-ex.h3c.com with ESMTP id 3993G8sm022033; Mon, 9 Oct 2023 11:16:17 +0800 (GMT-8) (envelope-from linchangwang.04414@h3c.com)
Received: from DAG2EX09-IDC.srv.huawei-3com.com (unknown [172.20.54.132]) by mail.maildlp.com (Postfix) with ESMTP id 3A5AC2005703; Mon, 9 Oct 2023 11:18:22 +0800 (CST)
Received: from DAG2EX07-IDC.srv.huawei-3com.com (172.20.54.130) by DAG2EX09-IDC.srv.huawei-3com.com (172.20.54.132) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256) id 15.1.2507.21; Mon, 9 Oct 2023 11:16:17 +0800
Received: from DAG2EX07-IDC.srv.huawei-3com.com ([::1]) by DAG2EX07-IDC.srv.huawei-3com.com ([fe80::fd0a:6e94:67d9:5ce8%10]) with mapi id 15.01.2507.006; Mon, 9 Oct 2023 11:16:17 +0800
From: linchangwang <linchangwang.04414@h3c.com>
To: Susan Hares <shares@ndzh.com>, "idr@ietf.org" <idr@ietf.org>
Thread-Topic: WG Adoption call for draft-peng-idr-segment-routing-te-policy-attr-05 (9/26/2023-10/10/2023)
Thread-Index: Adnw6cWQ9/etY0kqQcGCGiCUOrPsuwJdC55A
Date: Mon, 09 Oct 2023 03:16:17 +0000
Message-ID: <41d589c3c393450e93b34d3959cd7f57@h3c.com>
References: <BYAPR08MB487268B41AB9991CDA09CAC0B3C2A@BYAPR08MB4872.namprd08.prod.outlook.com>
In-Reply-To: <BYAPR08MB487268B41AB9991CDA09CAC0B3C2A@BYAPR08MB4872.namprd08.prod.outlook.com>
Accept-Language: zh-CN, en-US
Content-Language: zh-CN
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [10.114.76.67]
x-sender-location: DAG2
Content-Type: multipart/alternative; boundary="_000_41d589c3c393450e93b34d3959cd7f57h3ccom_"
MIME-Version: 1.0
X-DNSRBL:
X-SPAM-SOURCE-CHECK: pass
X-MAIL: h3cspam02-ex.h3c.com 3993G8sm022033
Archived-At: <https://mailarchive.ietf.org/arch/msg/idr/9iIwQm-fkEe3NK8SgaUW4Q9J_Is>
Subject: Re: [Idr] WG Adoption call for draft-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: Mon, 09 Oct 2023 03:17:01 -0000

Hi Sue,

I have reviewed this draft and I support the adoption of it.

My answers to your questions are as below.
1) Are these new segment types are useful for networks
Using alternate algorithms?

Yes.

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?

I see no issue with the alignment.


Thank you!

Best Regards,
Changwang


From: Idr [mailto:idr-bounces@ietf.org] On Behalf Of Susan Hares
Sent: Wednesday, September 27, 2023 10:33 AM
To: idr@ietf.org
Subject: [Idr] WG Adoption call for draft-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


-------------------------------------------------------------------------------------------------------------------------------------
?????????????????????????????????
????????????????????????????????????????
????????????????????????????????????????
???
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!

v2.23.0 | Report a Bug | By Email