Hi Linda,
Thanks a lot for taking the time to review the draft providing us with your 
valuable comments.
The authors will promptly review and address comments from you and other 
reviewers.

B.R.
Weiqiang Cheng
 
From: Linda Dunbar
Date: 2023-09-16 02:39
To: spring@ietf.org; draft-ietf-spring-srv6-srh-compress...@ietf.org
Subject: [spring] Review comments and questions to 
draft-ietf-spring-srv6-srh-compression-08
Weiqiang, clarence, Zhenbin, Bruno, and Francois, 
 
Reading through the draft-ietf-spring-srv6-srh-compression-08 for the first 
time without prior engagement in the discussion, I think the document is well 
written and clear. Here are some comments and questions:
 
Section 7.2 helps me the most in comprehending the mechanism described in the 
draft. It would be nice if adding a reference in Section 3 (Basic Concepts) to 
inform readers of the pseudo-code of the SR source node compressing the SID. 
 
Section 6.4 (Recommended Installation of C-SIDs in FIB):  The first sentence 
states that an SR segment endpoint node SHOULD install the corresponding FIB 
entry to match only the locator and function parts of SIDs. It is not clear who 
is responsible for installing the FIB entry? Is it by IGP? BGP or manual 
configuration? 
 
There are many acronyms, LBL, LNL, FL, LNFL, etc., used in the document. Can 
you list all of them in the Terminology section? 
 
Section 4.1.3: the pseudo code has “Set the packet’s associated FIB table to 
T”. I see it is also described in the RFC8986 for multi-table operation in the 
core. Can you elaborate what scenarios will a node have multi-table for IPv6 
forwarding? 
 
Section 5.1: states that “a Global C-SID typically identifies a shortest path 
to a node in the SRv6 domain”.  Earlier sections describe Global SID is a group 
of SID in the SRv6 domain. Isn’t “shortest Path” computed based on IGP 
advertisement? Why Global C-SID? 
 
 
Thank you, 
Linda
 
 
 
 
_______________________________________________
spring mailing list
spring@ietf.org
https://www.ietf.org/mailman/listinfo/spring

Reply via email to