Realisation after merging #148:
Next hop information can reside in multiple different places within a response, as the information is carried by different path attributes: the NEXT_HOP attribute for conventional IPv4 announcements, or within the MP_REACH_NLRI attribute for MP announcements.
This is technically correct and all, but, we should consider adding a generic next hop field outside of the actual path attributes, as a helper to the consumer of such responses.
Look into https://json-spec.readthedocs.io/reference.html
Realisation after merging #148:
Next hop information can reside in multiple different places within a response, as the information is carried by different path attributes: the
NEXT_HOPattribute for conventional IPv4 announcements, or within theMP_REACH_NLRIattribute for MP announcements.This is technically correct and all, but, we should consider adding a generic next hop field outside of the actual path attributes, as a helper to the consumer of such responses.
Look into https://json-spec.readthedocs.io/reference.html