<snip>
* You also suggest that Juniper’s is the only implementation. Are you sure that this is correct? There is a packet capture of CRH for anyone who is interested taken from our DPDK implementation – in this case – this is from the source node of traffic – steering through nodes 3 -> 2 -> 5 -> 5 -> 1 in our lab setup. https://www.gont.com.ar/packets/CRH.cap<https://www.gont.com.ar/packets/CRH.cap?fbclid=IwAR3gycrlv44jeEWQtRDifa189WdNG9fJ0uNpHer4hu7i_zGQfoyByObectY> So – there is certainly more than just Juniper working on this. Thanks Andrew Juniper Business Use Only From: Darren Dukes (ddukes) <ddu...@cisco.com> Sent: Monday, September 16, 2019 4:38 PM To: Ron Bonica <rbon...@juniper.net> Cc: Mark Smith <markzzzsm...@gmail.com>; EXT - daniel.bern...@bell.ca <daniel.bern...@bell.ca>; xie...@chinatelecom.cn; SPRING WG <spring@ietf.org>; 6man <6...@ietf.org>; Robert Raszuk <rob...@raszuk.net>; Rob Shakir <ro...@google.com>; Tarek Saad <tsaad.....@gmail.com> Subject: “SRV6+” complexity in forwarding Hi Ron, I agree ASICs are always improving, indeed this is evident in the number of successful SRv6 deployments and multiple vendor implementations at line rate on merchant silicon, and multiple vendor ASICs. Is “SRv6+” (PSSI+CRH+PPSI) implemented and deployed at line rate? You’ve been asked this several times. Since you’re the only implementor(?) and one operator is claiming deployment or testing, I am curious. Regardless of ASIC capabilities there are two performance penalties you will not escape with PSSI+CRH+PPSI: TLV parsing and multiple lookups. Requiring all segments in a CRH segment list to process an arbitrary length DOH+set of PSSI’s and other options is always very expensive. - It is expensive in SRAM as previously discussed in these threads. - It is expensive in parsing logic to know and process a set of TLVs in any ASIC or NP. Spreading PSSI, CRH, PPSI operations in multiple headers and multiple identifiers you now have multiple lookups at a node. 1 - lookup destination address 2 - lookup one or more PSSI and future destination options. 3 - lookup the CRH label or PPSI label. 4 - lookup new destination address Compare this with SRv6. 1 - lookup destination address 2 - lookup new destination address While ASICs are more capable and will continue to be more capable, these technical performance problems you introduce with PSSI+CRH+PPSI will not go away. Darren On Sep 12, 2019, at 12:34 PM, Ron Bonica <rbonica=40juniper....@dmarc.ietf.org<mailto:rbonica=40juniper....@dmarc.ietf.org>> wrote:
_______________________________________________ spring mailing list spring@ietf.org https://www.ietf.org/mailman/listinfo/spring
