Hi,

Please find below some comments on 
draft-ietf-spring-sr-redundancy-protection-06:

I'd suggest refining the Abstract along the lines:

   Redundancy Protection is a generalized protection mechanism to
   achieve high reliability for services provided in Segment Routing
   networks.  The mechanism uses the "Live-Live" methodology , i.e., multiple 
copies of the data packets are sent on different paths to provide protection.  
This
   document introduces one new SRv6 Segment Endpoint Behavior to provide
   replication and elimination functions on specific network nodes by
   leveraging SRv6 network programming capabilities.


I'd suggest refining the first paragraph in the Introduction along the lines:

   Redundancy Protection is a generalized protection mechanism to
   achieve the high reliability for services provided in a Segment
   Routing (SR) network.  Specifically, packets of flows are replicated
   at a replication network node into two or more copies, which are
   transported via different and disjoint paths in parallel.  On the
   elimination network node, only a single copy of the packet is forwarded, the 
redundant copies are eliminated.  This mechanism is commonly referred to as 
"Live-
   Live" as data traffic is forwarded on the protection paths simultaneously.  
One new SRv6 Segment Endpoint Behavior is introduced to
   provide the replication and elimination functions on specific network
   nodes by leveraging SRv6 network programming capabilities.  In case of 
redundancy protection, there is no need to perform switchover between 
protection paths as data packets are sent simultaneously on multiple protection 
paths.
Redundancy protection can facilitate to achieve zero
   packet loss target even when failure on either path happens.


Section 3:
It looks odd to me that Section 3 begins with a figure/
Afak, common practice is to have explanatory text before the figure.

I suggest to make the fist paragraph of the Section what is currently the first 
paragraph below the figure.


Section 3, item 6):

I understand that the specification of reordering is out od scope for this 
document.
However, it would be good to give a hint to the reader where to look for such 
specification.
I suggest adding an informative reference to RFC 9550 as an example.


Section 4:
I get the point of the Note.
However, it would be good to give a hint to the reader where to look for such 
specification.
I suggest adding an informative reference to IEEE Std 802.1CB-2017 as an 
example.
https://standards.ieee.org/ieee/802.1CB/5703/
https://ieeexplore.ieee.org/document/8091139


Section 4.1:
"protection need to be executed" -> "protection needs to be executed"

"In order to eliminate the redundant packet of a flow, elimination" -> "In 
order to eliminate the redundant packets of a flow, the elimination"


Best regards,
János
_______________________________________________
spring mailing list -- [email protected]
To unsubscribe send an email to [email protected]

Reply via email to