Compliance Test results for Quagga 0.99.24-rc1
----------------------------------------------
(based on Git commit 77ef0ac from February 6, 2015. This is the commit
just before the rc1 tag was added and is identical, except the version
number to the rc1)

For a complete testreport, see 
http://www.opensourcerouting.org/compliance-test-results/

Below is the summary of the new failures since recent release versions
If you plan to look at a specific bug and need more information,
then please feel free to ask.

Regards,
  Martin Winter
  OpenSourceRouting.org / (part of NetDEF)


==================================

Test: ANVL-BGPPLUS-15.14  (BGP IPv6)

Reference: RFC 4271, Sect. 5, p 23, Path Attributes
Class:   MUST
Summary: Path Attributes
        The sender of an UPDATE message should order path attributes within
        the UPDATE message in ascending order of attribute type.
        The receiver of an UPDATE message MUST be prepared to handle path
        attributes within the UPDATE message that are out of order.

Problem: Quagga does not put the attributes in ascending order
Fails since 0.99.23 - last released version is 0.99.22

Not a bug. There is an IDR draft being finalised which changes things 
so that MP_(UN)REACH_NLRI must come first in the attribute list. Other
attributes should remain in ascending order. 
See: https://tools.ietf.org/html/draft-ietf-idr-error-handling-18#section-5.1

Our compliance test suite ignores this draft

==================================

Test: ANVL-ISIS-2.4  (ISIS IPv4, Level-1)
Test: ANVL-ISIS-2.14  (ISIS IPv4, Level-2)

Reference: ISO/IEC 10589:1992(E) s9.8 p54-55 Level 1 Link State PDU
          RFC 1195 s5.3.4, p40-43 Level 1 Link State PDU
Reference: ISO/IEC 10589:1992(E) s9.9 p57-59 Level 2 Link State PDU
          RFC 1195 s5.3.5,p43-48 Level 2 Link State PDU
Class:   MUST
Summary: Link State PDU
        The valid codes that must be present in the VARIABLE LENGTH FIELD
         of level 1 link state PDU are:
          Area Addresses
          Intermediate system Neighbors
          Protocols Supported
          IP Interface Address
          IP internal Reachability Information

Problem: Level 1 Link State Packet incorrectly does not contain Intermediate 
        System Neighbours CLV  (1)
Worked in last released version (0.99.23.1), fails in current Quagga Git Master
ANVL-ISIS-2.14 is same issue for ISIS Level-2 and fails the same way

This error was actually there all the time, but the testscript was broken and
caused an incorrect "PASS" in the previous run. Fixed Test script which caused
other ISIS tests to pass, but failing this one.

==================================

Test: ANVL-ISIS-17.4  (ISIS IPv4, Level-1)
Test: ANVL-ISIS-17.10  (ISIS IPv4, Level-2)

Reference: RFC 1195 s5.3.4 P42 Level 1 Link State PDU
Reference: RFC 1195 s5.3.4 P45 Level 2 Link State PDU
Class:   MUST
Summary: Type of Service Routing
        Bit 7 of DEFAULT METRIC field (marked I/E) must be set to zero
        indicating internal metric

Problem: Received Level 1 Link State Packet without IS Neighbours' field
Worked in last released version (0.99.23.1), fails in current Quagga Git Master

ANVL-ISIS-17.10 is same issue for ISIS Level-2 and fails the same way

This error was actually there all the time, but the testscript was broken and
caused an incorrect "PASS" in the previous run. Fixed Test script which caused
other ISIS tests to pass, but failing this one.

==================================

Attachment: signature.asc
Description: Message signed with OpenPGP using GPGMail

_______________________________________________
Quagga-dev mailing list
[email protected]
https://lists.quagga.net/mailman/listinfo/quagga-dev

Reply via email to