Hi Cheng,
Here are some comments:
1. After supporting SRv6 compression, SL==0 does not necessarily indicate the
last segment endpoint node. Even when SL==0,
the destination address may contain up to 7 compressed uSIDs. The
following description needs to be revised.
Text:
S01. if SRH.P-flag processing is enabled:
S02. if intermediate node processing is disabled:
S03. if SRH.P-flag is set and SRH.SL == 0:
S03. SRv6 Path Segment processing
S04 else:
S05. if SRH.P-flag is set:
S06. SRv6 Path Segment processing
When the SRH.P-flag is set, the Path Segment processing is enabled.
In the cases that the intermediate processing of Path Segment is
disabled, a node will process the Path Segment only when it is the
last segment endpoint node indicating by SL == 0.
2. When encap.reduce is enabled and the SRv6 uSID mode is configured, there
might be only one SRv6 Path-segment in the SRH header. In such cases, is it
unable to support SRv6 Path-segment?
3. Can END.PSID be advertised, such as being advertised as a sub-TLV of SRv6
Locator in IGP and BGP-LS, similar to Section 8.4 of RFC8986? It is recommended
to clarify this.
4. For IANA values, it is recommended to follow RFC8986 and supplement
hexadecimal values.
5. Section 3.1 defines two methods: Locator and Local ID, and Global ID.
In actual development, most vendors use the Locator and Local ID method. It is
recommended not to retain the Global ID for the following reasons:
1) The SRv6 Path segment is carried in the SRH; assigning SID through a locator
is more appropriate.
2) No application scenarios for Global ID are seen; besides, Locator and Local
ID themselves form a unique global ID.
3) It is difficult to distinguish between the two allocation types.
6.Must the SRv6 Path segment be assigned by the egress, or should it be
determined based on the use case?
Thanks,
Changwang
-----邮件原件-----
发件人: Cheng Li <c.l=40huawei....@dmarc.ietf.org>
发送时间: 2024年9月2日 23:46
收件人: spring@ietf.org
抄送: draft-ietf-spring-srv6-path-segm...@ietf.org
主题: [spring] Request for MORE reviews of draft-ietf-spring-srv6-path-segment-09
Hi SPRING,
The SR-MPLS Path Segment draft has been published as RFC9545, and we think the
content of SRv6 Path Segment draft is quite stable and mature, so we hope to
see more tech reviews on it so that we can move the draft forward.
The draft is quite simple and straightforward, and it defines a new type of
segment called Path Segment, which is useful to identify an SRv6 path, similar
to SR-MPLS path segment.
The draft only defines the location that the SRv6 Path Segment should appear,
the possible general formats of it, and the general handling of Path Segment.
How to allocate the value to a Path Segment is out of the scope of this draft
and should be defined as per use cases.
An SRv6 Path Segment will not be used for routing so it should not be copied to
the IPv6 destination address.
Many thanks for Adrian, Stefano and Zafar for their useful comments and help on
this draft. More reviews and comments are welcome!
Thanks,
Cheng
-----Original Message-----
From: internet-dra...@ietf.org <internet-dra...@ietf.org>
Sent: Monday, September 2, 2024 5:15 PM
To: i-d-annou...@ietf.org
Cc: spring@ietf.org
Subject: [spring] I-D Action: draft-ietf-spring-srv6-path-segment-09.txt
Internet-Draft draft-ietf-spring-srv6-path-segment-09.txt is now available. It
is a work item of the Source Packet Routing in Networking (SPRING) WG of the
IETF.
Title: Path Segment for SRv6 (Segment Routing in IPv6)
Authors: Cheng Li
Weiqiang Cheng
Mach(Guoyi) Chen
Dhruv Dhody
Yongqing Zhu
Name: draft-ietf-spring-srv6-path-segment-09.txt
Pages: 13
Dates: 2024-09-02
Abstract:
Segment Routing (SR) allows for a flexible definition of end-to-end
paths by encoding an ordered list of instructions, called "segments".
The SR architecture can be implemented over an MPLS data plane as
well as an IPv6 data plane.
Currently, Path Segment has been defined to identify an SR path in
SR-MPLS networks, and is used for various use-cases such as end-to-
end SR Path Protection and Performance Measurement (PM) of an SR
path. This document defines the Path Segment to identify an SRv6
path in an IPv6 network.
The IETF datatracker status page for this Internet-Draft is:
https://datatracker.ietf.org/doc/draft-ietf-spring-srv6-path-segment/
There is also an HTMLized version available at:
https://datatracker.ietf.org/doc/html/draft-ietf-spring-srv6-path-segment-09
A diff from the previous version is available at:
https://author-tools.ietf.org/iddiff?url2=draft-ietf-spring-srv6-path-segment-09
Internet-Drafts are also available by rsync at:
rsync.ietf.org::internet-drafts
_______________________________________________
spring mailing list -- spring@ietf.org
To unsubscribe send an email to spring-le...@ietf.org
_______________________________________________
spring mailing list -- spring@ietf.org
To unsubscribe send an email to spring-le...@ietf.org
-------------------------------------------------------------------------------------------------------------------------------------
本邮件及其附件含有新华三集团的保密信息，仅限于发送给上面地址中列出
的个人或群组。禁止任何其他人以任何形式使用（包括但不限于全部或部分地泄露、复制、
或散发）本邮件中的信息。如果您错收了本邮件，请您立即电话或邮件通知发件人并删除本
邮件！
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!
_______________________________________________
spring mailing list -- spring@ietf.org
To unsubscribe send an email to spring-le...@ietf.org
