RIS Live's JSON UPDATE schema exposes only a small projection of BGP attributes (path, standard communities, origin, MED, aggregator, announcements, withdrawals). Attributes such as extended/large communities, local-pref, originator/cluster, MP_* details, OTC, AIGP, Prefix-SID, BIER, unknown/deprecated/raw attributes, etc. are not represented as JSON fields.
This means bgpkit-parser users parsing RIS Live JSON cannot access the full attribute set even when the parser supports those attributes. RIS Live supports socketOptions.includeRaw, which includes the original BGP wire message as data.raw. We should provide an opt-in raw parsing path while keeping the existing JSON-field parser available for backwards compatibility.
RIS Live's JSON UPDATE schema exposes only a small projection of BGP attributes (path, standard communities, origin, MED, aggregator, announcements, withdrawals). Attributes such as extended/large communities, local-pref, originator/cluster, MP_* details, OTC, AIGP, Prefix-SID, BIER, unknown/deprecated/raw attributes, etc. are not represented as JSON fields.
This means bgpkit-parser users parsing RIS Live JSON cannot access the full attribute set even when the parser supports those attributes. RIS Live supports socketOptions.includeRaw, which includes the original BGP wire message as data.raw. We should provide an opt-in raw parsing path while keeping the existing JSON-field parser available for backwards compatibility.