[#SXP-129] SXP can fallback to v1 from v2 only when the initiator is v1

[SXP-129] SXP can fallback to v1 from v2 only when the initiator is v1 Created: 12/Oct/17 Updated: 20/Jul/18
Status:	Open
Project:	sxp
Component/s:	General
Affects Version/s:	unspecified
Fix Version/s:	None

Type:

Bug

Reporter:

Martin Dindoffer

Assignee:

Unassigned

Resolution:

Unresolved

Votes:

Labels:

None

Remaining Estimate:

Not Specified

Time Spent:

Not Specified

Original Estimate:

Not Specified

Environment:

Operating System: All
Platform: All

External issue ID:

9281

Description

When the initiator of a v2 connection tries to connect to a v1 node, the connection fails because the v1 node sends back an error message.
The analogical opposite when a v1 node initiates a connection to v2 node succeeds with a v2 node falling back to v1.
===Example===
This can be rarely observed in Basic csit test suite:
https://logs.opendaylight.org/releng/jenkins092/sxp-csit-1node-basic-all-carbon/421/

Comments

Comment by Martin Dindoffer [ 20/Jul/18 ]

This is due to conformance with a highly confidential Cisco spec.

Generated at Wed Feb 07 20:40:01 UTC 2024 using Jira 8.20.10#820010-sha1:ace47f9899e9ee25d7157d59aa17ab06aee30d3d.

[SXP-129] SXP can fallback to v1 from v2 only when the initiator is v1 Created: 12/Oct/17 Updated: 20/Jul/18