Changes between Version 9 and Version 10 of draft-ietf-idr-rfc8203bis


Ignore:
Timestamp:
Sep 12, 2019, 8:55:06 AM (5 weeks ago)
Author:
santiago@…
Comment:

Update about BIRD

Legend:

Unmodified
Added
Removed
Modified
  • draft-ietf-idr-rfc8203bis

    v9 v10  
    44||Juniper||Junos 19.1R1||Jeff Haas||https://www.juniper.net/documentation/en_US/junos/topics/reference/configuration-statement/protocols-bgp-shutdown.html
    55||OpenBSD||OpenBGPD 6.6||Job||https://github.com/openbsd/src/commit/0521032199a5c6ef3fd42399ca72fff762336379||
    6 ||NIC.CZ||BIRD x.x||Job||https://gitlab.labs.nic.cz/labs/bird/commit/7ff34ca2cb86f3947bf049f73e76e6ce5d57e4a8||
     6||CZ.NIC||BIRD 1.6.8 / 2.0.6||Job||https://gitlab.labs.nic.cz/labs/bird/commit/7ff34ca2cb86f3947bf049f73e76e6ce5d57e4a8||
    77
    88
     
    1010
    1111||section|| function ||Required|| JunOS supports||OpenBSD supports||BIRD supports||
    12 ||2||Subcode values- only 2 and 4||MUST||yes||(yes/no))||(yes/no))||
    13 ||2||Send Shutdown messages in UTF-8||MUST||yes||(yes/no))||(yes/no))||
    14 ||2||Receive Shutdown messages in UTF-8||MUST||yes||(yes/no))||(yes/no))||
    15 ||2||Field is not NUL terminated||MUST||yes||(yes/no))||(yes/no))||
    16 ||2||Shutdown reports included in syslog||SHOULD||no||(yes/no))||(yes/no))||
    17 ||4||Error Handling includes error messages for invalid length||SHOULD||no [1]||(yes/no))||(yes/no))||
    18 ||4||Error Handling includes error messages for invalid length with hex dump||SHOULD||no [1]||(yes/no))||(yes/no))||
     12||2||Subcode values- only 2 and 4||MUST||yes||(yes/no))||yes||
     13||2||Send Shutdown messages in UTF-8||MUST||yes||(yes/no))||agnostic[2]||
     14||2||Receive Shutdown messages in UTF-8||MUST||yes||(yes/no))||agnostic[2]||
     15||2||Field is not NUL terminated||MUST||yes||(yes/no))||yes||
     16||2||Shutdown reports included in syslog||SHOULD||no||(yes/no))||yes||
     17||4||Error Handling includes error messages for invalid length||SHOULD||no [1]||(yes/no))||yes||
     18||4||Error Handling includes error messages for invalid length with hex dump||SHOULD||no [1]||(yes/no))||partial||
    1919
    2020[1] - There is an open PR (defect report) covering reception of invalid UTF-8 sequences.  The current behavior is to truncate overly long shutdown strings to the maximum permitted length prior to display.  Upon fixing of the open issue, improperly formed UTF-8 characters will be trimmed.
     21
     22[2] - Does not recode, will send and display UTF-8 correctly if CLI runs in terminal with UTF-8 active (which is almost always today)