https://jira.opendaylight.org This file is an XML representation of an issue en-us 8.20.10 820010 22-06-2022 https://jira.opendaylight.org/browse/BGPCEP-921 bgpcep <p>When parsing a computation request containing multiple bandwidth objects of different types, ODL fail and send a "Missing RP Object" error back to the PCC. I got the error sending a custom bandwidth object from Cisco, but <a href="https://jira.opendaylight.org/secure/ViewProfile.jspa?name=odd22" class="user-hover" rel="odd22">odd22</a> confirmed it would fail with a proper type 2 bandwidth object too. Attached is a packet capture showing the problem.</p> BGPCEP-921

Parsing a computation request with multiple bandwidth objects fails with wrong error

Bug Medium Open Unresolved Olivier Dugeon Sebastien Merle Mon, 24 Aug 2020 09:24:13 +0000 Tue, 12 Jul 2022 08:36:29 +0000 PCEP 0 2 <p>The packet capture shows that 2 Bandwidth Objects are transmitted with PCEP Object Class 5 (which is correct). The first Bandwidth Object (5) is of type 1 (Requested Bandwidth) but the second one if of type 5 which is unknown. According to iana, this Object Type (5) for this Object Class (5) is unassigned (see <a href="https://www.iana.org/assignments/pcep/pcep.xhtml#pcep-objects" class="external-link" target="_blank" rel="nofollow noopener">https://www.iana.org/assignments/pcep/pcep.xhtml#pcep-objects</a> ).</p> <p>Thus, it is normal that ODL send a PCerr message. Now, I agree that the error message should be of type 3 (Unknown Object) with error value equal to 2 (Unrecognised Object Type) and not of type 6 (Mandatory Object Missing) with value equal to 1 (RP object missing).</p> <p>This mismatch is due to the validation process within ODL parsing. If the RP Object is not conform, parser returns null, and ODL consider that the RP Object is missing while the parser should return the error type and error value.</p> Development Rank 0|i03ulz: