https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=14241
--- Comment #12 from Garri <g.djavad...@gmail.com> ---
Below is important note from the RFC 7911 [1], related to the issue:
---------
The only explicit indication that the encoding described in Section 3
is in use in a particular BGP session is the exchange of Capabilities
described in Section 4. If the exchange is successful [RFC5492],
then the BGP speakers will be able to process all BGP UPDATES
properly, as described in Section 5. However, if, for example, a
packet analyzer is used on the wire to examine an active BGP session,
it may not be able to properly decode the BGP UPDATES because it
lacks prior knowledge of the exchanged Capabilities.
---------
If I understand It correctly, Wireshark should decode NLRI as Add-path capable
only if it seen Open messages exchange with Add-path capabilities.
[1] https://tools.ietf.org/html/rfc7911#section-6
--
You are receiving this mail because:
You are watching all bug changes.
___________________________________________________________________________
Sent via: Wireshark-bugs mailing list <wireshark-bugs@wireshark.org>
Archives: https://www.wireshark.org/lists/wireshark-bugs
Unsubscribe: https://www.wireshark.org/mailman/options/wireshark-bugs
mailto:wireshark-bugs-requ...@wireshark.org?subject=unsubscribe
