I’ve a community seize of a real-live BGP-LS session:
...
Path attributes
Path Attribute - ORIGIN: IGP
Path Attribute - AS_PATH: empty
Path Attribute - LOCAL_PREF: 100
Path Attribute - BGP-LS Attribute
Flags: 0x80, Optionally available, Non-transitive, Full
Sort Code: BGP-LS Attribute (29)
Size: 97
Hyperlink State
Administrative group (shade) TLV
Most hyperlink bandwidth TLV
Most reservable hyperlink bandwidth TLV
Unreserved bandwidth TLV
TE Default Metric TLV
Metric TLV
Adjacency SID TLV
Adjacency SID TLV
Path Attribute - MP_REACH_NLRI
Flags: 0x90, Optionally available, Prolonged-Size, Non-transitive, Full
Sort Code: MP_REACH_NLRI (14)
Size: 228
Tackle household identifier (AFI): BGP-LS (16388)
Subsequent handle household identifier (SAFI): BGP-LS (71)
Subsequent hop:
Variety of Subnetwork factors of attachment (SNPA): 0
Community Layer Reachability Data (NLRI)
BGP-LS NLRI
BGP-LS NLRI
BGP-LS NLRI
...
… the place one can observe inside a BGP replace message within the MP_REACH_NLRI path attribute a number of BGP-LS NLRIs (Hyperlink-NLRIs). Additionally throughout the BGP-LS path attribute there are a number of “Adjacency SID TLV (Sort 1099)”.
I’m of the opinion that this isn’t appropriate.
“[BGP-LS attribute] is used to hold hyperlink, node, and prefix parameters and attributes” – in my understanding – for a single particular BGP-LS NLRI, if we might have a number of BGP-LS NLRIs inside a MP_REACH_NLRI attribute then I do not know for which of these the particular BGP-LS attribute TLVs are meant.
Are a number of BGP-LS NLRIs in a single MP_REACH_NLRI path attribute permitted?
I’ve a community seize of a real-live BGP-LS session:
...
Path attributes
Path Attribute - ORIGIN: IGP
Path Attribute - AS_PATH: empty
Path Attribute - LOCAL_PREF: 100
Path Attribute - BGP-LS Attribute
Flags: 0x80, Optionally available, Non-transitive, Full
Sort Code: BGP-LS Attribute (29)
Size: 97
Hyperlink State
Administrative group (shade) TLV
Most hyperlink bandwidth TLV
Most reservable hyperlink bandwidth TLV
Unreserved bandwidth TLV
TE Default Metric TLV
Metric TLV
Adjacency SID TLV
Adjacency SID TLV
Path Attribute - MP_REACH_NLRI
Flags: 0x90, Optionally available, Prolonged-Size, Non-transitive, Full
Sort Code: MP_REACH_NLRI (14)
Size: 228
Tackle household identifier (AFI): BGP-LS (16388)
Subsequent handle household identifier (SAFI): BGP-LS (71)
Subsequent hop:
Variety of Subnetwork factors of attachment (SNPA): 0
Community Layer Reachability Data (NLRI)
BGP-LS NLRI
BGP-LS NLRI
BGP-LS NLRI
...
… the place one can observe inside a BGP replace message within the MP_REACH_NLRI path attribute a number of BGP-LS NLRIs (Hyperlink-NLRIs). Additionally throughout the BGP-LS path attribute there are a number of “Adjacency SID TLV (Sort 1099)”.
I’m of the opinion that this isn’t appropriate.
“[BGP-LS attribute] is used to hold hyperlink, node, and prefix parameters and attributes” – in my understanding – for a single particular BGP-LS NLRI, if we might have a number of BGP-LS NLRIs inside a MP_REACH_NLRI attribute then I do not know for which of these the particular BGP-LS attribute TLVs are meant.
Are a number of BGP-LS NLRIs in a single MP_REACH_NLRI path attribute permitted?
