thomas king and arnold nipper pointed out an omission which this fills

   A route server is usually 'transparent', most importantly not
   inserting its own AS into the AS_Path, to not lengthen the AS hop
   count and thereby reduce the likelihood of best path selection.  See
   2.2.2 of [I-D.ietf-idr-ix-bgp-route-server].  A BGPsec-aware route
   server needs to validate the incoming BGPSEC_Path, and to forward
   updates which can be validated by clients which know the route
   server's AS.  The route server uses pCount of zero to not increase
   the effective AS hop count.

randy

_______________________________________________
sidr mailing list
[email protected]
https://www.ietf.org/mailman/listinfo/sidr

Reply via email to