Re: [Idr] [idr] Comments Summary about [draft-lin-idr-sr-policy-seglist-id]

[[e-mail]]

Hi, 

About bullet 1, I agree that the sid list id and path segment are different. The sid list id is mainly used in control plane and will not be used for packet encapsulation, while the path segment will be used in the packet.




Regards,

Yao















Original



From: linchangwang <[e-mail]>
To: [e-mail] <[e-mail]>;
Date: 2023年04月03日 20:23
Subject: [Idr] [idr] Comments Summary about [draft-lin-idr-sr-policy-seglist-id]



Hi wg,
 
We received several comments on the 116 IDR meeting about the following draft:https://datatracker.ietf.org/doc/draft-lin-idr-sr-policy-seglist-id/
A new version of the draft https://www.ietf.org/archive/id/draft-lin-idr-sr-policy-seglist-id-03.txt  is published.
 
According to Jeffrey’s request, we make a summary here so that discussions can be continued:
 
1. Path-Segment (https://datatracker.ietf.org/doc/draft-ietf-idr-sr-policy-path-segment/) provides similar functionality. (By Aijun & Cheng)
 
The path-segment is used to identify on the forwarding plane, not the management plane.
In the case that both PCE and YANG are identified by ID and name, it is suggested that the segment-list should also have the identification of the management plane.
The application scenarios are also different. Path-segment is used for performance measurement, path correlation, and end-2-end path protection.
But our use cases are statistics reporting and configuration delivery.
 
2. Segment-List-Protection (https://datatracker.ietf.org/doc/draft-lp-idr-sr-path-protection/) also defines List Identifier Sub-TLV. (By Yao)
 
draft-lp-idr-sr-path-protection describes a protection mechanism for segment list, and defines a 4-octet List Identifier which is used to describe the correlation between protected segment list and backup segment list.The segment list protection might also be an application scenario of segment-list id. But we think it’s better to have an independent draft for segment-list id.
On the other hand, we also defines the segment-list name sub-TLV in our draft, which are more operationally friendly.
 
3. ID conflictions between Segment List configured in the headnode and Segment List ceated by controller. (By Ka)
 
There are several possible solutions:
A. ID is unique per candidate path, not unique globally at a headend. (The path-ID in PCEP works in this way)
B. The headend organizes segment lists by originator in the top-level, and then by ID in the second-level.
 
4. Discussions about the name/id of the sr-policy template (https://datatracker.ietf.org/doc/draft-zhang-idr-sr-policy-template/)
 
Those discussions are about another draft, but we think the segment list identifier can have the same issue.
Names are more operationally friendly. IDs are easier for implementation.
Both the segment-list name sub-TLV and segment-list ID sub-TLV are defined in our draft to achieve better flexibility.
 
Any comments would be helpful. Please don’t hesitate to let us know.
 
Thanks,
Changwang lin
 
 
 
-----Original Message-----
From: I-D-Announce [mailto:[e-mail]] On Behalf Of [e-mail]
Sent: Monday, April 03, 2023 7:14 PM
To: [e-mail]
Subject: I-D Action: draft-lin-idr-sr-policy-seglist-id-03.txt
 
 
A New Internet-Draft is available from the on-line Internet-Drafts
directories.
 
   Title           : BGP SR Policy Extensions for Segment List Identifier
   Authors         : Changwang Lin
                     Weiqiang Cheng
                     Yao Liu
                     Ketan Talaulikar
                     Mengxiao Chen
   Filename        : draft-lin-idr-sr-policy-seglist-id-03.txt
   Pages           : 8
   Date            : 2023-04-03
 
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 datatracker status page for this Internet-Draft is:
https://datatracker.ietf.org/doc/draft-lin-idr-sr-policy-seglist-id/
 
There is also an htmlized version available at:
https://datatracker.ietf.org/doc/html/draft-lin-idr-sr-policy-seglist-id-03
 
A diff from the previous version is available at:
https://author-tools.ietf.org/iddiff?url2=draft-lin-idr-sr-policy-seglist-id-03
 
Internet-Drafts are also available by rsync at rsync.ietf.org::internet-drafts
 
 
_______________________________________________
I-D-Announce mailing list
[e-mail]
https://www.ietf.org/mailman/listinfo/i-d-announce
Internet-Draft directories: http://www.ietf.org/shadow.html
or ftp://ftp.ietf.org/ietf/1shadow-sites.txt
-------------------------------------------------------------------------------------------------------------------------------------
本邮件及其附件含有新华三集团的保密信息，仅限于发送给上面地址中列出
的个人或群组。禁止任何其他人以任何形式使用（包括但不限于全部或部分地泄露、复制、
或散发）本邮件中的信息。如果您错收了本邮件，请您立即电话或邮件通知发件人并删除本
邮件！
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!
_______________________________________________
Idr mailing list
[e-mail]
https://www.ietf.org/mailman/listinfo/idr