originatingConnectionId incorrect in reserveTimeout message.

[jmacauley]

When the reservation reserveTimeout event is return by an aggregator OpenNSA on PacificWave I get the following content:

reserveTimeout {
    providerNSA = urn:ogf:network:lsanca.pacificwave.net:2016:nsa,
    correlationId = urn:uuid:3846121e-fe6b-11ea-af4e-525400c57fcf,
    connectionId = LS-cd202541ea,
    notificationId = 46,
    timeStamp = 2020-09-24T13:38:24.723135Z,
    originatingNSA = urn:ogf:network:lsanca.pacificwave.net:2016:nsa,
    originatingConnectionId = JUNOS-711498,
    timeoutValue = 120
}

In this case the “originatingConnectionId” should be set to “LS-cd202541ea” since this NSA is the originating NSA of the timeout. If the aggregator had exposed the underlying uPA then the “originatingNSA” field would have been set to that uPA, and then “originatingConnectionId” as the connectionId in the context of the uPA. However, since there is no visibility of an NSA other than “urn:ogf:network:lsanca.pacificwave.net:2016:nsa” we need it set to “LS-cd202541ea” since this is the uPA reservation in the context of NSI.