Changes between Version 47 and Version 48 of draft-ietf-idr-bgp-extended-implementations


Ignore:
Timestamp:
Sep 12, 2019, 8:40:19 AM (6 weeks ago)
Author:
santiago@…
Comment:

Update about BIRD

Legend:

Unmodified
Added
Removed
Modified
  • draft-ietf-idr-bgp-extended-implementations

    v47 v48  
    88* BGPSEC-IO - BGP Sec traffic generator that allows generating multihop BGPsec updates
    99* ExaBGP - Reported by Thomas Mangin
    10 * OpenDaylight- supported by the BGP module from Boron release onwards 
     10* OpenDaylight- supported by the BGP module from Boron release onwards
     11* BIRD - optional, since version 1.6.0 
    1112
    1213* if you know details of the reported implementations, please add details on the list. These can be 3rd party reports on the implementation.
     
    1415== Implementation Reports ==
    1516
    16 || # || Protocol Feature  || QuaggaSRx || BGPSEC-IO || ExaBGP || OpenDayLight ||
    17 || 1 || Announce via BGP Capability advertisement (RFC5492) as BGP Extended Message Capability || Yes || Yes || Yes || Yes ||
    18 || 2  || If Extended Message Capability supported,  Implementation MUST be able to receive an UPDATE message larger than 4096 bytes  || Yes || Yes || Yes || Yes ||
    19 || 3  || Applications putting data into BGP Extended messages MUST limit size of payload to handle max message size || Yes || Yes || Yes || Yes ||
    20 || 4  || Supports Extended message, but peer has not advertised BGP Extended Message Capability || ||  || || ||
    21 || 4a || SHOULD NOT accept Extended message || Yes || Yes || Yes || Yes ||
    22 || 4b || MAY Accept Extended message (config/implementation knob) || Yes || Yes || Yes || No ||
    23 || 4c || Does send Extended Message   || Yes || Yes || Yes  || Yes ||
     17|| # || Protocol Feature  || QuaggaSRx || BGPSEC-IO || ExaBGP || OpenDayLight || BIRD ||
     18|| 1 || Announce via BGP Capability advertisement (RFC5492) as BGP Extended Message Capability || Yes || Yes || Yes || Yes || Yes ||
     19|| 2  || If Extended Message Capability supported,  Implementation MUST be able to receive an UPDATE message larger than 4096 bytes  || Yes || Yes || Yes || Yes || Yes ||
     20|| 3  || Applications putting data into BGP Extended messages MUST limit size of payload to handle max message size || Yes || Yes || Yes || Yes || Yes ||
     21|| 4  || Supports Extended message, but peer has not advertised BGP Extended Message Capability || ||  || || || ||
     22|| 4a || SHOULD NOT accept Extended message || Yes || Yes || Yes || Yes || Yes ||
     23|| 4b || MAY Accept Extended message (config/implementation knob) || Yes || Yes || Yes || No || No ||
     24|| 4c || Does send Extended Message   || Yes || Yes || Yes  || Yes || Yes ||
    2425|| 5  || Error handing || yes  || yes  ||  yes ||  ||
    25 || 5a || Accepts Extended message without receiving BGP Extended Message Capability [Section 5 paragraph 1 MAY] ||  ||   ||  ||  No ||
    26 || 5b || If receives Extended Message without BGP extended message support, follows RFC4271 handling and sends Bad message length Notification [section 5 paragraph 2 MUST]  || Yes || Yes || Yes || Yes ||
     26|| 5a || Accepts Extended message without receiving BGP Extended Message Capability [Section 5 paragraph 1 MAY] ||  ||   ||  ||  No || No ||
     27|| 5b || If receives Extended Message without BGP extended message support, follows RFC4271 handling and sends Bad message length Notification [section 5 paragraph 2 MUST]  || Yes || Yes || Yes || Yes || Yes ||
    2728
    2829== Management Information ==