[#BGPCEP-163] Endpoint obj is missing in the PCInitiateMessage

[BGPCEP-163] Endpoint obj is missing in the PCInitiateMessage Created: 07/Nov/14 Updated: 03/Mar/19 Resolved: 07/Nov/14
Status:	Resolved
Project:	bgpcep
Component/s:	PCEP
Affects Version/s:	Bugzilla Migration
Fix Version/s:	Bugzilla Migration

Type:

Bug

Reporter:

Bin Pan

Assignee:

Unassigned

Resolution:

Cannot Reproduce

Votes:

Labels:

None

Remaining Estimate:

Not Specified

Time Spent:

Not Specified

Original Estimate:

Not Specified

Environment:

Operating System: All
Platform: All

External issue ID:

2338

Description

I checkec the code of SrPcInitiateMessageParser.java and found the endpoint Obj is missing in the serializeRequest() method.

It is MUST according to the http://tools.ietf.org/html/draft-crabbe-pce-pce-initiated-lsp-03#section-5.1.

LSP instantiation

The END-POINTS Object is mandatory for an instantiation request of an
RSVP-signaled LSP. It contains the source and destination addresses
for provisioning the LSP. If the END-POINTS Object is missing, the
PCC MUST send a PCErr message with Error-type=6 (Mandatory Object
missing) and Error-value=3 (END-POINTS Object missing).

------------------------------------------
ODL Version: Heilum/stable.

Comments

Comment by Dana Kutenicsova [ 07/Nov/14 ]

But it's not required according: http://tools.ietf.org/html/draft-sivabalan-pce-segment-routing-02#section-4.3

SrPcInitiateMessageParser is segment-routing proprietary (and in version 03 will be dropped). What you are reffering to is class CInitiated00PCInitiateMessageParser which does contain EndPoints object.

Generated at Wed Feb 07 19:12:13 UTC 2024 using Jira 8.20.10#820010-sha1:ace47f9899e9ee25d7157d59aa17ab06aee30d3d.

[BGPCEP-163] Endpoint obj is missing in the PCInitiateMessage Created: 07/Nov/14 Updated: 03/Mar/19 Resolved: 07/Nov/14