[OPSAWG]Re: [spring] Re: Fw: New Version Notification for draft-liu-opsawg-ipfix-path-segment-00.txt

[[e-mail]]

Hi Changwang,

Path segment is put at the last entry(e.g, segment list[N]) in the SRH. But there's no convenient method if we only want to export  segment list[N].
Leveraging RFC9487, the last entry can be carried via srhSegmentIPv6ListSection/srhSegmentIPv6BasicList, but in this way , the whole segment list would be included in IPFIX message starting from segment list[0].
And although IE "srhSegmentIPv6" represents a 128-bit SRv6 segment, how to decode it relies on the context, that is, if only one srhSegmentIPv6 appears in the IPFIX message, there's no information to indicate the position of this segment in the list.

Thanks,
Yao



 







Original


From: linchangwang <[e-mail]>
To: 刘尧00165286;[e-mail] <[e-mail]>;[e-mail] <[e-mail]>;
Cc: [e-mail] <[e-mail]>;
Date: 2025年03月01日 09:45
Subject: [spring] Re: Fw: New Version Notification for draft-liu-opsawg-ipfix-path-segment-00.txt

_______________________________________________
spring mailing list -- [e-mail]
To unsubscribe send an email to [e-mail]
 

Hi Yao,
 
https://datatracker.ietf.org/doc/rfc9487/, RFC9487 can now export SRH header information.
 By using the flag in the SRH and combining it with the corresponding path-segment, the path can be identified.
 Are there other considerations for the new expansions defined in the document?
 
Thanks,
Changwang
 

发件人: [e-mail] <[e-mail]> 
 发送时间: 2025年2月18日 18:09
 收件人: [e-mail]; [e-mail]
 抄送: [e-mail]
 主题: [spring] Fw: New Version Notification for draft-liu-opsawg-ipfix-path-segment-00.txt


 
Dear OPSAWG and SPRING,
 
A new draft https://datatracker.ietf.org/doc/html/draft-liu-opsawg-ipfix-path-segment  has just been submitted.
This document introduces a new IPFIX Information Element(IE) to identify the Path Segment Identifier(PSID) in the SRH for SRv6 path identification purpose. 
While the detailed segment list information can already be exported in IPFIX as specified in RFC9487, a path identifier would make it more convenient to distinguish  segment lists in some usecases. As the concept of PSID has already been adopted by SPRING, the authors think that introducing a new IE for PSID would be a direct method.
 
Any feedback or comments are more than welcome.
 
Thanks,
Yao
 
 
 
 

Original

From: [e-mail] <[e-mail]>



Date: 2025年02月18日 17:37



Subject: New Version Notification for draft-liu-opsawg-ipfix-path-segment-00.txt




A new version of Internet-Draft draft-liu-opsawg-ipfix-path-segment-00.txt has
 been successfully submitted by Yao Liu and posted to the
 IETF repository.
 
 Name:     draft-liu-opsawg-ipfix-path-segment
 Revision: 00
 Title:    Export of Path Segment Identifier Information in IPFIX
 Date:     2025-02-18
 Group:    Individual Submission
 Pages:    6
 URL:      https://www.ietf.org/archive/id/draft-liu-opsawg-ipfix-path-segment-00.txt
 Status:   https://datatracker.ietf.org/doc/draft-liu-opsawg-ipfix-path-segment/
 HTML:     https://www.ietf.org/archive/id/draft-liu-opsawg-ipfix-path-segment-00.html
 HTMLized: https://datatracker.ietf.org/doc/html/draft-liu-opsawg-ipfix-path-segment
 
 
 Abstract:
 
    This document introduces a new IPFIX Information Element to identify
    the Path Segment Identifier(PSID) in the SRH for SRv6 path
    identification purpose.
 
 
 
 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!